Re: Statement-level triggers and inheritance

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, Greg Sabino Mullane <greg(at)turnstep(dot)com>
Subject: Re: Statement-level triggers and inheritance
Date: 2009-01-18 09:50:09
Message-ID: 200901181150.10592.peter_e@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sunday 18 January 2009 08:24:47 Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > On Thursday 15 January 2009 02:08:42 Bruce Momjian wrote:
> >> Added to TODO:
> >> Have statement-level triggers fire for all tables in an
> >> inheritance hierarchy
> >
> > I don't think that was really the conclusion from the thread.
> >
> > As far as I can interpret the opinions, statement level triggers should
> > fire on the parent table only, rather than on some child, as it currently
> > does.
>
> I think the consensus was that each table should have its own statement
> triggers (if any) fire. Which is one possible reading of Bruce's TODO
> item, but it's surely not clearly worded.

We should also consult the SQL standard. Its language regarding inheritance
is sometimes not in line with our implementation (see recent discussion about
GRANT).

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2009-01-18 09:56:51 Re: Fixes for compiler warnings
Previous Message alanwli 2009-01-18 07:10:16 Re: Fixes for compiler warnings