Re: ALTER TABLE ... NOREWRITE option

From: "Petr Jelinek" <pjmodos(at)pjmodos(dot)net>
To: "'Andres Freund'" <andres(at)2ndquadrant(dot)com>, "'Josh Berkus'" <josh(at)agliodbs(dot)com>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ALTER TABLE ... NOREWRITE option
Date: 2012-12-01 20:45:39
Message-ID: 000001cdd004$d33820d0$79a86270$@pjmodos.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> -----Original Message-----
> From: pgsql-hackers-owner(at)postgresql(dot)org [mailto:pgsql-hackers-
> owner(at)postgresql(dot)org] On Behalf Of Andres Freund
> Sent: 01 December 2012 21:40
> To: Josh Berkus
> Cc: pgsql-hackers(at)postgresql(dot)org
> Subject: Re: [HACKERS] ALTER TABLE ... NOREWRITE option
>
> On 2012-12-01 12:35:15 -0800, Josh Berkus wrote:
> >
> > > If you have a framework and you want to test for this you can just
> > > compare relfilenodes before/after.
> >
> > You're targeting the wrong users. This feature isn't for helping you
> > or me. It's for helping the Rails users.
>
> I am not targeting anything. All I am saying is that if some framework
(not the
> framework's users!) wants to build something like that today its not all
that
> complicated.

I would prefer to be able to detect this *before* the rewrite happens though
when writing tooling.

Regards
Petr Jelinek

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-12-01 20:47:28 Re: PITR potentially broken in 9.2
Previous Message Andrew Dunstan 2012-12-01 20:41:15 Re: --single-transaction hack to pg_upgrade does not work