Re: PANIC: failed to re-find parent key in "100924" for split pages 1606/1673

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: valiouk(at)yahoo(dot)co(dot)uk, pgsql-bugs(at)postgresql(dot)org
Subject: Re: PANIC: failed to re-find parent key in "100924" for split pages 1606/1673
Date: 2009-01-08 18:16:17
Message-ID: 1231438577.18005.228.camel@ebony.2ndQuadrant
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


On Mon, 2009-01-05 at 14:25 -0500, Tom Lane wrote:
> val <valiouk(at)yahoo(dot)co(dot)uk> writes:
> > I have a database that refuses to start due to the afformentioned error. I am running POstgreSQL 8.1.11 on a Debian Etch box.
>
> > Jan 5 10:36:29 db2 postgres[17111]: [11-1] PANIC: failed to re-find parent key in "100924" for split pages 1606/1673
>
> Hmm ... I wonder if this is telling us that our patch here was
> incomplete?
> http://archives.postgresql.org/pgsql-committers/2006-11/msg00004.php
>
> At the time we thought this failure could only occur during _bt_pagedel
> but you have evidently got a case where a split is failing. It might
> just be garden-variety index corruption, or it might be a real bug.

Did you catch this had occurred during recovery?

Can we downgrade the error from PANIC to LOG please? One corrupt index
shouldn't prevent us from restarting the whole server. Plus, if we have
to use pg_resetxlog to get us out of trouble it isn't going to help much
with diagnosis. We can rebuild indexes once server is up.

--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2009-01-08 18:40:33 Re: PANIC: failed to re-find parent key in "100924" for split pages 1606/1673
Previous Message Art Lembo 2009-01-08 01:49:14 BUG #4605: Role Privileges don't show up in PGAdmin