Re: ALTER TABLE ... NOREWRITE option

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: ALTER TABLE ... NOREWRITE option
Date: 2012-12-04 02:44:33
Message-ID: 2105.1354589073@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Josh Berkus <josh(at)agliodbs(dot)com> writes:
>> EXPLAIN ALTER TABLE would be the next step I guess. I discovered plenty
>> of magic tricks when working on the rewriting support for that command,
>> and I think exposing them in the EXPLAIN output would go a long way
>> towards reducing some POLA violations.

> I think this would be cool on its own merits.

> 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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2012-12-04 02:52:46 Re: json accessors
Previous Message Josh Berkus 2012-12-04 01:54:45 Re: ALTER TABLE ... NOREWRITE option