Skip site navigation (1) Skip section navigation (2)

Re: Statement-level triggers and inheritance

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Greg Sabino Mullane" <greg(at)turnstep(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Statement-level triggers and inheritance
Date: 2008-11-28 21:59:19
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
"Greg Sabino Mullane" <greg(at)turnstep(dot)com> writes:
> Looks like inheritance causes a statement-level trigger to fire on
> the last evaluated table in the inheritance chain. Is this the
> desired behavior?

Hm, I think whoever wrote the statement-level trigger code completely
forgot to consider the possibility of multiple target relations.  It's
not even consistent between BEFORE and AFTER triggers for this case.

My feeling is that it ought to fire such triggers on *each* target.

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Greg StarkDate: 2008-11-28 22:01:33
Subject: Re: Fixing contrib/isn for float8-pass-by-value
Previous:From: Greg Sabino MullaneDate: 2008-11-28 21:34:09
Subject: Statement-level triggers and inheritance

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group