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 19:15:45
Message-ID: 1231442145.18005.260.camel@ebony.2ndQuadrant
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2009-01-08 19:19:37 Re: PANIC: failed to re-find parent key in "100924" for split pages 1606/1673
Previous Message Tom Lane 2009-01-08 18:40:33 Re: PANIC: failed to re-find parent key in "100924" for split pages 1606/1673