Re: ALTER TABLE ... NOREWRITE option

From: "Petr Jelinek" <pjmodos(at)pjmodos(dot)net>
To: "'Andres Freund'" <andres(at)2ndquadrant(dot)com>
Cc: "'Simon Riggs'" <simon(at)2ndQuadrant(dot)com>, "'Robert Haas'" <robertmhaas(at)gmail(dot)com>, "'Dimitri Fontaine'" <dimitri(at)2ndquadrant(dot)fr>, "'Josh Berkus'" <josh(at)agliodbs(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ALTER TABLE ... NOREWRITE option
Date: 2012-12-06 19:59:38
Message-ID: 004601cdd3ec$399e9850$acdbc8f0$@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: 06 December 2012 20:44
> To: Petr Jelinek
> Cc: 'Simon Riggs'; 'Robert Haas'; 'Dimitri Fontaine'; 'Josh Berkus';
pgsql-
> hackers(at)postgresql(dot)org
> Subject: Re: [HACKERS] ALTER TABLE ... NOREWRITE option
> > > Event triggers get called *during* the ALTER TABLE. So if were not
> > > careful they see something thats not easy to handle.
> > >
> >
> > I thought the point of this was to call the trigger *before* anything
> > happens.
>
> Just because the rewrite hasn't started yet, doesn't mean nothing else has
> been changed.
>
> Note, I am not saying this is impossible or anything, the original point
drawn
> into question was that we need to be especially careful with choosing
> callsites and thats its not trivial to do right.
>

Ok my assumption is that the event would be fired before ALTER actually did
anything, firing triggers while DDL is actually already being executed seems
like bad idea.

Regards
Petr Jelinek

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Claudio Freire 2012-12-06 20:05:09 Re: Slow query: bitmap scan troubles
Previous Message Andres Freund 2012-12-06 19:43:42 Re: ALTER TABLE ... NOREWRITE option