Skip site navigation (1) Skip section navigation (2)

Re: Nasty btree deletion bug

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Nasty btree deletion bug
Date: 2006-10-26 17:21:53
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
"Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> writes:
> But now that I look at the original post by Ed, I don't see how the 
> "failed to re-find parent key" error could result from the issue we've 
> been talking about. The error message is printed when _bt_getstackbuf is 
> unable to re-find an item in the parent of a deleted page, but 
> _bt_getstackbuf doesn't look at or compare the keys at all.

Right, but _bt_getstackbuf is working from a search stack created by
a standard search for the victim page's high key.  If that search
descended through a page to the right of the victim page's actual
parent, _bt_getstackbuf isn't able to recover.

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Joshua D. DrakeDate: 2006-10-26 17:32:55
Subject: Re: NOTICE: word is too long INSERT 0 3014
Previous:From: Heikki LinnakangasDate: 2006-10-26 17:08:10
Subject: Re: Nasty btree deletion bug

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group