| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, 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 06:24:47 |
| Message-ID: | 23903.1232259887@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-01-18 06:28:51 | Re: Fixes for compiler warnings |
| Previous Message | Tom Lane | 2009-01-18 06:15:42 | Re: Autovacuum daemon terminated by signal 11 |