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

Re: triggers and inheritance tree

From: Jaime Casanova <jaime(at)2ndquadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: triggers and inheritance tree
Date: 2012-03-28 14:46:18
Message-ID: CAJKUy5ho-jwTXLQxsehFsCZs-kvVCm_v7ajHrSwbEqTRUE9Z=g@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Wed, Mar 28, 2012 at 8:29 AM, Robert Haas <robertmhaas(at)gmail(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2012-03-28 14:57:51
Subject: Re: Re: pg_stat_statements normalisation without invasive changes to the parser (was: Next steps on pg_stat_statements normalisation)
Previous:From: Peter GeogheganDate: 2012-03-28 14:45:25
Subject: Re: Re: pg_stat_statements normalisation without invasive changes to the parser (was: Next steps on pg_stat_statements normalisation)

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