Postgres Pro
Downloads
Home   >   mailing lists

Re: serializable lock consistency - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: serializable lock consistency
Date
Msg-id 4D0EF4C2.7070208@enterprisedb.com
Whole thread Raw
In response to Re: serializable lock consistency  (Florian Pflug <fgp@phlo.org>)
Responses Re: serializable lock consistency  (Florian Pflug <fgp@phlo.org>)
List pgsql-hackers
Tree view 
On 19.12.2010 20:57, Florian Pflug wrote:
> If we reuse the legacy field xvac to store xlast, we don't get into
> trouble with binary upgrades either. We' need to find a way to deal
> with tuples where HEAP_MOVED_IN or HEAP_MOVED_OUT is set, but that
> seems manageable..

xvac shares the field with command id, and cid is in use while the tuple 
is being updated.

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Itagaki Takahiro
Date:
Subject: Re: Extensions and custom_variable_classes
Next
From: Alex Hunsaker
Date:
Subject: Re: plperlu problem with utf8