Re: Hot standby and GiST page splits (was Re: WIP: Fast GiST index build) - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Hot standby and GiST page splits (was Re: WIP: Fast GiST index build)
Date
Msg-id CA+U5nMKV7TR9vqgas2Yq+4Ekw7NpGC59Z5mH3CRR5-V0szrKvA@mail.gmail.com
Whole thread Raw
In response to Re: Hot standby and GiST page splits (was Re: WIP: Fast GiST index build)  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: Hot standby and GiST page splits (was Re: WIP: Fast GiST index build)
List pgsql-hackers
On Mon, Aug 1, 2011 at 2:29 PM, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.com> wrote:
> On 01.08.2011 14:35, Simon Riggs wrote:
>>
>> On Mon, Aug 1, 2011 at 11:44 AM, Heikki Linnakangas
>> <heikki.linnakangas@enterprisedb.com>  wrote:
>>
>>>> Does the order of locking of the buffers matter? I'm sure it does.
>>>
>>> Yep.
>>
>> Do you mean that the BlockNumbers are already in correct sequence, or
>> that you will be adding this code to redo?
>
> I just meant that yes, the order of locking of the buffers does matter.
>
> I believe we code acquire the locks in right order already, and the patch I
> posted fixes the premature release of locks at page split.

Your patch is good, but it does rely on the idea that we're logging
the blocks in the same order they were originally locked. That's a
good assumption, but I would like to see that documented for general
sanity, or just mine at least.

I can't really see anything in the master-side code that attempts to
lock things in a specific sequence, which bothers me also.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Hot standby and GiST page splits (was Re: WIP: Fast GiST index build)
Next
From: Heikki Linnakangas
Date:
Subject: Re: Hot standby and GiST page splits (was Re: WIP: Fast GiST index build)