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

From Hiroshi Inoue
Subject RE: btree split logic is fragile in the presence of lar ge index items
Date
Msg-id 001701bff1e3$4dd15d60$2801007e@tpf.co.jp
Whole thread Raw
In response to RE: btree split logic is fragile in the presence of lar ge index items  ("Mikheev, Vadim" <vmikheev@SECTORBASE.COM>)
List pgsql-hackers
> -----Original Message-----
> From: Mikheev, Vadim
> 
> > > > 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.
>

Currently the page contains the leftmost key is the target page of
insertion and is locked exclusively but it may be different in extra
TID implementation. There may be a very rare deadlock possibility.
Hiroshi Inoue
Inoue@tpf.co.jp 


pgsql-hackers by date:

Previous
From: Chris Bitmead
Date:
Subject: Re: Re: [GENERAL] PRIMARY KEY & INHERITANCE (fwd)
Next
From: "Stephan Szabo"
Date:
Subject: Re: Re: [GENERAL] PRIMARY KEY & INHERITANCE (fwd)