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>
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 01:39:09
Message-ID: 8F4C99C66D04D4118F580090272A7A23018C67@SECTORBASE1
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> > > 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.

First, Tom is not going to do TID implementation now...
But anyway while we hold lock on a page we are able to go right
and lock pages (and we do this now). There is no possibility for
deadlock here: backward scans always unlock page before reading/locking
left page.

Vadim

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Larry Rosenman 2000-07-20 02:14:06 mac.c
Previous Message Stephan Szabo 2000-07-20 00:50:06 Re: Re: [GENERAL] PRIMARY KEY & INHERITANCE (fwd)