Re: FOR KEY LOCK foreign keys

Alvaro Herrera <alvherre@commandprompt.com>

From: Alvaro Herrera <alvherre@commandprompt.com>

To: Noah Misch <noah@leadboat.com>

Cc: Pg Hackers <pgsql-hackers@postgresql.org>, Dimitri Fontaine <dimitri@2ndquadrant.fr>

Date: 2011-02-14T20:56:10Z

Lists: pgsql-hackers

Excerpts from Noah Misch's message of vie feb 11 04:13:22 -0300 2011:

> I observe visibility breakage with this test case:
>
>  [ ... ]
>
> The problem seems to be that funny t_cid (2249).  Tracing through heap_update,
> the new code is not setting t_cid during this test case.

So I can fix this problem by simply adding a call to
HeapTupleHeaderSetCmin when the stuff about ComboCid does not hold, but
seeing that screenful plus the subsequent call to
HeapTupleHeaderAdjustCmax feels wrong.  I think this needs to be
rethought ...

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support