RE: btree split logic is fragile in the presence of lar ge index items

From: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>
Cc: <pgsql-hackers(at)postgreSQL(dot)org>
Subject: RE: btree split logic is fragile in the presence of lar ge index items
Date: 2000-07-19 23:45:39
Message-ID: 000e01bff1db$71b6cb00$2801007e@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> -----Original Message-----
> From: pgsql-hackers-owner(at)hub(dot)org [mailto:pgsql-hackers-owner(at)hub(dot)org]On
> Behalf Of Tom Lane
>
> "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mikheev, Vadim 2000-07-20 00:17:11 RE: btree split logic is fragile in the presence of lar ge index items
Previous Message Chris Bitmead 2000-07-19 23:43:37 Re: [HACKERS] Re: PRIMARY KEY & INHERITANCE (fwd)