Postgres Pro
Downloads
Home   >   mailing lists

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

From Simon Riggs
Subject Re: PANIC: failed to re-find parent key in "100924" for split pages 1606/1673
Date
Msg-id 1231442145.18005.260.camel@ebony.2ndQuadrant
Whole thread Raw
In response to Re: PANIC: failed to re-find parent key in "100924" for split pages 1606/1673  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: PANIC: failed to re-find parent key in "100924" for split pages 1606/1673  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Tree view 
On Thu, 2009-01-08 at 13:40 -0500, Tom Lane wrote:
>
> > Can we downgrade the error from PANIC to LOG please?
>
> No, that seems utterly unsafe to me.  We'd have a corrupt index and
> nothing to cause it to get repaired.

We do exactly this with GIN and GIST indexes currently.

I'd rather have a database that works, but has a corrupt index than one
that won't come up at all.

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

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: PANIC: failed to re-find parent key in "100924" for split pages 1606/1673
Next
From: Tom Lane
Date:
Subject: Re: PANIC: failed to re-find parent key in "100924" for split pages 1606/1673