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

From: "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>
To: "'Hiroshi Inoue'" <Inoue(at)tpf(dot)co(dot)jp>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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-20 00:17:11
Message-ID: 8F4C99C66D04D4118F580090272A7A23018C65@SECTORBASE1
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephan Szabo 2000-07-20 00:18:17 Re: Re: [GENERAL] PRIMARY KEY & INHERITANCE (fwd)
Previous Message Hiroshi Inoue 2000-07-19 23:45:39 RE: btree split logic is fragile in the presence of lar ge index items