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

From Tom Lane
Subject Re: _bt_parent_deletion_safe() isn't safe
Date
Msg-id 9158.1276025752@sss.pgh.pa.us
Whole thread Raw
In response to _bt_parent_deletion_safe() isn't safe  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: _bt_parent_deletion_safe() isn't safe  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
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.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: hstore ==> and deprecate =>
Next
From: Robert Haas
Date:
Subject: Re: hstore ==> and deprecate =>