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

Re: _bt_parent_deletion_safe() isn't safe

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org, Jeff Amiel <becauseimjeff(at)yahoo(dot)com>
Subject: Re: _bt_parent_deletion_safe() isn't safe
Date: 2010-07-02 23:20:41
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Tom Lane wrote:
> I wrote:
> > I realized this while thinking about Jeff Amiel's report here:
> >
> > 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(at)momjian(dot)us>

  + None of us is going to be here forever. +

In response to


pgsql-hackers by date

Next:From: Andrew DunstanDate: 2010-07-02 23:30:17
Subject: Re: [COMMITTERS] pgsql: Allow copydir() to be interrupted.
Previous:From: Robert HaasDate: 2010-07-02 21:47:20
Subject: Re: warning message in standby

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