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

From Stephen R. van den Berg
Subject Re: BUG #2667: vacuuming a 70GB table causes a "crash"
Date
Msg-id 64b4daae0609301934l75ba5317y4946d9a4089a6c48@mail.gmail.com
Whole thread Raw
In response to Re: BUG #2667: vacuuming a 70GB table causes a "crash"  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #2667: vacuuming a 70GB table causes a "crash"  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On 9/30/06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> "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:

My postgres.conf file says:

full_page_writes = off

As I understand it, the 8.1.4 postgres ignores this setting?
--
Sincerely,
                Stephen R. van den Berg (AKA BuGless).

pgsql-bugs by date:

Previous
From: "Bill Hernandez"
Date:
Subject: BUG #2668: The config dir was empty -> cannot find install-sh or install.sh in config ./config
Next
From: Tom Lane
Date:
Subject: Re: BUG #2669: The config dir was empty -> cannot find install-sh or install.sh in config ./config