Re: FOR KEY LOCK foreign keys - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: FOR KEY LOCK foreign keys
Date
Msg-id 1297716803-sup-1524@alvh.no-ip.org
Whole thread Raw
In response to Re: FOR KEY LOCK foreign keys  (Noah Misch <noah@leadboat.com>)
List 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


pgsql-hackers by date:

Previous
From: Chris Browne
Date:
Subject: Re: why two dashes in extension load files
Next
From: Stephen Frost
Date:
Subject: Re: ALTER TYPE 2: skip already-provable no-work rewrites