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:13:32
Message-ID: 12732.1332375212@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> Specifically, I'm wondering if we couldn't get away with rearranging
>> things so that the root line pointer (which has index entries) points
>> to the actual tuple, and the other line pointer (which can't have any
>> index entries) gets marked UNUSED.

> This would amount to changing the TID of the live row.

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-03-22 00:24:24 Re: Proposal: Create index on foreign table
Previous Message Tom Lane 2012-03-22 00:09:48 Re: HOT updates & REDIRECT line pointers