From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
---|---|
To: | Peter Geoghegan <pg(at)heroku(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Failure while inserting parent tuple to B-tree is not fun |
Date: | 2013-10-22 17:30:35 |
Message-ID: | 5266B63B.2010208@vmware.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 22.10.2013 20:27, Peter Geoghegan wrote:
> On Tue, Oct 22, 2013 at 9:55 AM, Heikki Linnakangas
> <hlinnakangas(at)vmware(dot)com> wrote:
>> I propose that we use the same approach I used with GiST, and add a flag to
>> the page header to indicate "the downlink hasn't been inserted yet". When
>> insertion (or vacuum) bumps into a flagged page, it can finish the
>> incomplete action by inserting the downlink.
>
> Sounds very reasonable, but I'm interested in how you intend to
> structure things, given this sounds like what could loosely be called
> btree private state. I may also need to use a flag bit for something
> that is of interest to the btree code alone.
I may be missing something, but there are already plenty of b-tree
specific flags. See BTP_* in nbtree.h. I'll just add another to that list.
- Heikki
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2013-10-22 17:45:27 | Re: Failure while inserting parent tuple to B-tree is not fun |
Previous Message | Peter Geoghegan | 2013-10-22 17:27:38 | Re: Failure while inserting parent tuple to B-tree is not fun |