| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Noah Misch <noah(at)leadboat(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr> |
| Subject: | Re: FOR KEY LOCK foreign keys |
| Date: | 2011-02-14 20:56:10 |
| Message-ID: | 1297716803-sup-1524@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2011-02-14 21:06:59 | Re: ALTER TYPE 2: skip already-provable no-work rewrites |
| Previous Message | Chris Browne | 2011-02-14 20:37:11 | Re: why two dashes in extension load files |