Re: serializable lock consistency

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Florian Pflug <fgp(at)phlo(dot)org>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: serializable lock consistency
Date: 2010-12-20 06:16:34
Message-ID: 4D0EF4C2.7070208@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alex Hunsaker 2010-12-20 07:39:17 Re: plperlu problem with utf8
Previous Message Itagaki Takahiro 2010-12-20 05:22:31 Re: Extensions and custom_variable_classes