RE: btree split logic is fragile in the presence of lar ge index items - Mailing list pgsql-hackers

From Mikheev, Vadim
Subject RE: btree split logic is fragile in the presence of lar ge index items
Date
Msg-id 8F4C99C66D04D4118F580090272A7A23018C65@SECTORBASE1
Whole thread Raw
Responses RE: btree split logic is fragile in the presence of lar ge index items  ("Hiroshi Inoue" <Inoue@tpf.co.jp>)
List pgsql-hackers
> > > Do not add TID to key but store key anywhere in duplicate 
> > > chain and just read lefter child page while positioning index scan,
> > > as we do right now for partial keys?
> > 
> > > This will result in additional reads but I like it much more than
> > > current "logic"...
> >
> 
> What about unique key insertions ?

We'll have to find leftmost key in this case and do what we do now.

Vadim


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: btree split logic is fragile in the presence of lar ge index items
Next
From: Chris Bitmead
Date:
Subject: Re: Re: [GENERAL] PRIMARY KEY & INHERITANCE (fwd)