"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