Re: [PATCHES] HOT WIP Patch - version 2 - Mailing list pgsql-hackers

From Pavan Deolasee
Subject Re: [PATCHES] HOT WIP Patch - version 2
Date
Msg-id 2e78013d0702200704x447ced85hd6e62c0002c0ae01@mail.gmail.com
Whole thread Raw
In response to Re: [PATCHES] HOT WIP Patch - version 2  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers

On 2/20/07, Bruce Momjian <bruce@momjian.us> wrote:
Tom Lane wrote:
>
> "Recently dead" means "still live to somebody", so those tids better not
> change either.  But I don't think that's what he meant.  I'm more
> worried about the deadlock possibilities inherent in trying to upgrade a
> buffer lock.  We do not have deadlock detection for LWLocks.

I am guessing he is going to have to release the lock, then ask for an
exclusive one.

Yes, thats what is done. Since we try to prune the HOT-update chain
even in the SELECT path, we upgrade the lock only if we are sure
that there is atleast one tuple that can be removed from the chain
or the root needs to be fixed (broken ctid chain for some reason).
 
Thanks,
Pavan

--

EnterpriseDB     http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: "Pavan Deolasee"
Date:
Subject: Re: HOT WIP Patch - version 2
Next
From: "Jonah H. Harris"
Date:
Subject: Re: New feature request: FlashBack Query