Re: HOT updates & REDIRECT line pointers

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: HOT updates & REDIRECT line pointers
Date: 2012-03-22 00:44:08
Message-ID: 13203.1332377048@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Wed, Mar 21, 2012 at 8:13 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Another issue, quite independent from race conditions against other
>> observers of the row, is what if the tuple is part of an update chain?
>> You have no way to find the predecessor row version and update its
>> t_ctid forward link.

> I don't see why I need to. The predecessor, if any, points to the
> root of the HOT chain;

Oh, right. So scratch that objection. The other one is still fatal
though ...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2012-03-22 00:50:24 heap_freeze_tuple locking requirements
Previous Message Robert Haas 2012-03-22 00:41:33 Re: HOT updates & REDIRECT line pointers