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 000e01bff1db$71b6cb00$2801007e@tpf.co.jp
Whole thread Raw
In response to Re: btree split logic is fragile in the presence of lar ge index items  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: btree split logic is fragile in the presence of lar ge index items
List pgsql-hackers
> -----Original Message-----
> From: pgsql-hackers-owner@hub.org [mailto:pgsql-hackers-owner@hub.org]On
> Behalf Of Tom Lane
> 
> "Mikheev, Vadim" <vmikheev@SECTORBASE.COM> writes:
> >> Do you not like the proposal I was suggesting?  I thought it 
> >> was pretty much what you said yourself a few months ago...
> 
> > 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 ?

Regards.

Hiroshi Inoue


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Shared library search paths
Next
From: Chris Bitmead
Date:
Subject: Re: Re: [GENERAL] PRIMARY KEY & INHERITANCE (fwd)