Re: Block B-Tree concept - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Block B-Tree concept
Date
Msg-id 16785.1159545459@sss.pgh.pa.us
Whole thread Raw
In response to Re: Block B-Tree concept  (Heikki Linnakangas <heikki@enterprisedb.com>)
Responses Re: Block B-Tree concept  (Heikki Linnakangas <heikki@enterprisedb.com>)
List pgsql-hackers
Heikki Linnakangas <heikki@enterprisedb.com> writes:
> Tom Lane wrote:
>> define "consecutive".

> I don't mean consecutive as in "1, 2, 3, 4, ... without gaps" but as in 
> "A and B are consecutive in the index, if there's no value X in the 
> index so that A < X < B". Maybe there's a better word for that.

Um, but how are you going to make that work without storing the keys for
both A and B?  You won't be able to tell whether an incoming key C
that's just a bit bigger than A should go before or after B.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Another idea for dealing with cmin/cmax
Next
From: Tom Lane
Date:
Subject: Array assignment behavior (was Re: [ADMIN] Stored procedure array limits)