Re: surprising trigger/foreign key interaction

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: surprising trigger/foreign key interaction
Date: 2009-08-12 23:04:27
Message-ID: 14750.1250118267@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)commandprompt(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-08-12 23:19:42 Re: schemapg.h
Previous Message Tom Lane 2009-08-12 23:02:06 Re: Error message for FK referencing deferrable unique/PK