Re: BUG #2667: vacuuming a 70GB table causes a "crash"

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Stephen R(dot) van den Berg" <srb(at)cuci(dot)nl>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2667: vacuuming a 70GB table causes a "crash"
Date: 2006-09-30 21:01:38
Message-ID: 16939.1159650098@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Stephen R. van den Berg" <srb(at)cuci(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2006-09-30 21:02:46 Re: BUG #2660: Cannot install ISN extension when charset=UTF88
Previous Message Stephen R. van den Berg 2006-09-30 13:16:15 BUG #2667: vacuuming a 70GB table causes a "crash"