Re: _bt_parent_deletion_safe() isn't safe - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: _bt_parent_deletion_safe() isn't safe
Date
Msg-id 201007022320.o62NKfZ12063@momjian.us
Whole thread Raw
In response to Re: _bt_parent_deletion_safe() isn't safe  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: _bt_parent_deletion_safe() isn't safe
List pgsql-hackers
Tom Lane wrote:
> I wrote:
> > I realized this while thinking about Jeff Amiel's report here:
> > http://archives.postgresql.org/pgsql-general/2010-06/msg00351.php
> > I can't prove that this is what's causing his crashes, but it could
> > produce the symptom he's reporting.
> 
> Actually, no it can't: the case I'm envisioning should lead to throwing
> this error:
> 
>     elog(ERROR, "failed to delete rightmost child %u of block %u in index \"%s\"",
>          target, parent, RelationGetRelationName(rel));
> 
> a bit further up.  That's annoying enough, but it's not a PANIC.
> 
> A search of the archives produces no evidence that anyone has ever
> reported the "failed to delete rightmost child" error from the field.
> So while I still think this is a bug that needs to be fixed, it may
> be lower priority than I thought initially.

Is this a TODO?

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + None of us is going to be here forever. +


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: warning message in standby
Next
From: Andrew Dunstan
Date:
Subject: Re: [COMMITTERS] pgsql: Allow copydir() to be interrupted.