Re: BUG #5664: index "idx000_mytable19" contains unexpected zero page

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "simon" <xubochin(at)163(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5664: index "idx000_mytable19" contains unexpected zero page
Date: 2010-09-20 05:17:37
Message-ID: 20916.1284959857@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"simon" <xubochin(at)163(dot)com> writes:
> Description: index "idx000_mytable19" contains unexpected zero page
> ...
> 4. After the concurrent execution is complete, the system powers off.
> ...
> The following solutions are provided in almost all forums:
> 1. Set fsync to on (The parameter is set to on in the current version).

If you're implying that you ran a test involving power loss with fsync
off, then this is not a bug. Even if you had fsync on, I would wonder
about whether your disk drives execute fsync properly.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Graham 2010-09-20 17:03:15 BUG #5665: VPATH catalog/schemapg.h
Previous Message simon 2010-09-20 05:06:06 BUG #5664: index "idx000_mytable19" contains unexpected zero page