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

From: "Stephen R(dot) van den Berg" <srb(at)cuci(dot)nl>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2667: vacuuming a 70GB table causes a "crash"
Date: 2006-10-01 02:34:21
Message-ID: 64b4daae0609301934l75ba5317y4946d9a4089a6c48@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 9/30/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "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:

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).

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2006-10-01 18:55:40 Re: BUG #2664: date_trunc('quarter', ...)
Previous Message Bill Hernandez 2006-09-30 23:54:53 BUG #2669: The config dir was empty -> cannot find install-sh or install.sh in config ./config