Re: BUG #2667: vacuuming a 70GB table causes a "crash" - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #2667: vacuuming a 70GB table causes a "crash"
Date
Msg-id 16939.1159650098@sss.pgh.pa.us
Whole thread Raw
In response to BUG #2667: vacuuming a 70GB table causes a "crash"  ("Stephen R. van den Berg" <srb@cuci.nl>)
Responses Re: BUG #2667: vacuuming a 70GB table causes a "crash"
List pgsql-bugs
"Stephen R. van den Berg" <srb@cuci.nl> writes:
> datalog=# vacuum verbose fnetsense;
> INFO:  vacuuming "public.fnetsense"
> PANIC:  right sibling is not next child in "fnetsense_utstamp_key"
> server closed the connection unexpectedly

Were you running with full_page_writes off during some earlier use of
this database?  There is a known failure mode that can produce this
situation in 8.1.x for x < 4, see thread here:

http://archives.postgresql.org/pgsql-bugs/2006-04/msg00135.php

> Restarted the server, didn't help.  Error is persistent
> now, DB is still working, don't know how to repair the
> DB.

REINDEX that index.

            regards, tom lane

pgsql-bugs by date:

Previous
From: "how to cluster"
Date:
Subject: BUG #2666: how do cluster with 7.4.13 ?
Next
From: Tom Lane
Date:
Subject: Re: BUG #2660: Cannot install ISN extension when charset=UTF88