Re: Foreign key trigger timing bug? - Mailing list pgsql-hackers

From Stephan Szabo
Subject Re: Foreign key trigger timing bug?
Date
Msg-id 20051207134621.V49571@megazone.bigpanda.com
Whole thread Raw
In response to Foreign key trigger timing bug?  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Foreign key trigger timing bug?
Re: Foreign key trigger timing bug?
List pgsql-hackers
On Wed, 7 Dec 2005, Bruce Momjian wrote:

> I had an open 8.1 item that was:
>
>     o  fix foreign trigger timing issue
>
> Would someone supply text for a TODO entry on this, as I don't think we
> fixed it in 8.1.

I'd split this into two separate items now.
Fix before delete triggers on cascaded deletes to run after the cascaded
delete is done.  This is odd, but seems to be what the spec requires.
Fix problems with referential action caused before triggers that modify
rows that would also be modified by the referential action.  Right now,
this has a few symptoms, either you can get spurious seeming errors from
the constraint or you can end up with invalid data in the referencing
table. As far as I can see, the spec doesn't have much to say about this
because the spec doesn't seem to allow before triggers to modify tables.


pgsql-hackers by date:

Previous
From: Darcy Buskermolen
Date:
Subject: Re: Foreign key trigger timing bug?
Next
From: Tom Lane
Date:
Subject: Reducing contention for the LockMgrLock