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: | 201007022320.o62NKfZ12063@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ None of us is going to be here forever. +
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2010-07-02 23:30:17 | Re: [COMMITTERS] pgsql: Allow copydir() to be interrupted. |
Previous Message | Robert Haas | 2010-07-02 21:47:20 | Re: warning message in standby |