Re: triggers and inheritance tree - Mailing list pgsql-hackers

From Jaime Casanova
Subject Re: triggers and inheritance tree
Date
Msg-id CAJKUy5ho-jwTXLQxsehFsCZs-kvVCm_v7ajHrSwbEqTRUE9Z=g@mail.gmail.com
Whole thread Raw
In response to Re: triggers and inheritance tree  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: triggers and inheritance tree  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Wed, Mar 28, 2012 at 8:29 AM, Robert Haas <robertmhaas@gmail.com> wrote:
>
> I think the problem is that the UPDATE or DELETE can only fire once a
> matching row has been identified, so that OLD can be filled in
> appropriately.  But in this case, the matching row gets found not in
> the parent table, but in one of its child tables.  So any triggers on
> the child table would fire, but triggers on the parent table will not.
>

ah! and of course that makes a lot of sense...
how embarrasing! :(

--
Jaime Casanova         www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación


pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Re: pg_stat_statements normalisation without invasive changes to the parser (was: Next steps on pg_stat_statements normalisation)
Next
From: Tom Lane
Date:
Subject: Re: Re: pg_stat_statements normalisation without invasive changes to the parser (was: Next steps on pg_stat_statements normalisation)