Re: 3rd time is a charm.....right sibling is not next child crash.

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jeff Amiel <becauseimjeff@yahoo.com>
Cc: pgsql-general@postgresql.org
Date: 2010-06-08T16:23:56Z
Lists: pgsql-hackers
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:  right sibling 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