Re: Frequent Update Project: Design Overview of HOT Updates - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Frequent Update Project: Design Overview of HOT Updates
Date
Msg-id 16166.1163136468@sss.pgh.pa.us
Whole thread Raw
In response to Re: Frequent Update Project: Design Overview of HOT Updates  ("Pavan Deolasee" <pavan.deolasee@gmail.com>)
Responses Re: Frequent Update Project: Design Overview of HOT Updates  ("Pavan Deolasee" <pavan.deolasee@gmail.com>)
List pgsql-hackers
"Pavan Deolasee" <pavan.deolasee@gmail.com> writes:
> On 11/10/06, Josh Berkus <josh@agliodbs.com> wrote:
>> I believe that's the "unsolved technical issue" in the prototype, unless
>> Pavan has solved it in the last two weeks.   Pavan?
>> 
> When an overflow tuple is copied back to the main heap, the overflow tuple
> is
> marked with a special flag (HEAP_OVERFLOW_MOVEDBACK). Subsequently,
> when a backend tries to lock the overflow version of the tuple, it checks
> the flag
> and jumps to the main heap if the flag is set.

(1) How does it "jump to the main heap"?  The links go the other
direction.

(2) Isn't this full of race conditions?

(3) I thought you already used up the one remaining t_infomask bit.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Pavan Deolasee"
Date:
Subject: Re: Frequent Update Project: Design Overview of HOT Updates
Next
From: "Pavan Deolasee"
Date:
Subject: Re: Frequent Update Project: Design Overview of HOT Updates