Re: surprising trigger/foreign key interaction - Mailing list pgsql-hackers

From Tom Lane
Subject Re: surprising trigger/foreign key interaction
Date
Msg-id 14750.1250118267@sss.pgh.pa.us
Whole thread Raw
In response to Re: surprising trigger/foreign key interaction  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: surprising trigger/foreign key interaction  (Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>)
Re: surprising trigger/foreign key interaction  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> writes:
> However I'm guessing that what actually happens is that heap_update is
> returning HeapTupleSelfUpdated instead, which the code states as
> /* nothing to do */.

Yeah.

> I imagine this is so because of some old fiddling to get semantics just
> right for obscure corner cases, but it feels wrong nevertheless.

I suspect it was reluctance to use the EvalPlanQual semantics (which
are pretty bogus in their own way) for perfectly deterministic
single-transaction cases.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Error message for FK referencing deferrable unique/PK
Next
From: Robert Haas
Date:
Subject: Re: schemapg.h