Re: 3rd time is a charm.....right sibling is not next child crash. - Mailing list pgsql-general

From Tom Lane
Subject Re: 3rd time is a charm.....right sibling is not next child crash.
Date
Msg-id 6257.1276014236@sss.pgh.pa.us
Whole thread Raw
In response to 3rd time is a charm.....right sibling is not next child crash.  (Jeff Amiel <becauseimjeff@yahoo.com>)
Responses Re: 3rd time is a charm.....right sibling is not next child crash.  (Jeff Amiel <jamiel@istreamimaging.com>)
List pgsql-general
Jeff Amiel <becauseimjeff@yahoo.com> writes:
> New one yesterday.

> Jun  7 15:05:01 db-1 postgres[9334]: [ID 748848 local0.crit] [3989781-1] 2010-06-07 15:05:01.087 CDT    9334PANIC:
rightsibling 169 of block 168 is not next child of 249 in index "sl_seqlog_idx" 

In your original report you mentioned that the next autovacuum attempt
on the same table succeeded without incident.  Has that been true each
time?  I wonder whether this is some transient state, rather than actual
corruption that you need to REINDEX to recover from.

            regards, tom lane

pgsql-general by date:

Previous
From: p.buongiovanni@net-international.com
Date:
Subject: Re: BUG #5492: Sequence corruption
Next
From: Aaron Burnett
Date:
Subject: Some insight on the proper SQL would be appreciated