Re: ALTER TABLE ... NOREWRITE option - Mailing list pgsql-hackers

From Tom Lane
Subject Re: ALTER TABLE ... NOREWRITE option
Date
Msg-id 18520.1354660229@sss.pgh.pa.us
Whole thread Raw
In response to Re: ALTER TABLE ... NOREWRITE option  (Josh Berkus <josh@agliodbs.com>)
Responses Re: ALTER TABLE ... NOREWRITE option  (Simon Riggs <simon@2ndQuadrant.com>)
Re: ALTER TABLE ... NOREWRITE option  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
Josh Berkus <josh@agliodbs.com> writes:
>>> However, for a very large user group -- users with ORMs which do their
>>> own DDL migrations -- we could also use a way to log or WARN for table
>>> rewrites.  Since the ORMs are not gonna do an EXPLAIN.

>> An ORM is also quite unlikely to pay attention to a warning, much less a
>> postmaster log entry ... so your argument seems unfounded from here.

> But the DevOps staff *is*.

Sure, and the DevOps staff would be using the EXPLAIN feature (if we had
it).  After which they could do little anyway except complain to the ORM
authors, who might or might not give a damn.  I don't see that there's
enough value-added from what you suggest to justify the development
time.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: WIP: store additional info in GIN index
Next
From: Tom Lane
Date:
Subject: Re: WIP: store additional info in GIN index