From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Adam Kruger" <ackruger(at)hotmail(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #1731: Indexes are corrupt following an unclean shutdown |
Date: | 2005-06-25 23:23:30 |
Message-ID: | 3215.1119741810@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
"Adam Kruger" <ackruger(at)hotmail(dot)com> writes:
> I have encountered a condition similar to those referenced at:
> http://archives.postgresql.org/pgsql-admin/2005-06/msg00051.php
> and
> http://archives.postgresql.org/pgsql-bugs/2005-06/msg00142.php
> I have come up with a simple method for reproducing this error condition.
Thanks for the test case. The solution (at least for the near future)
seems to be to force a checkpoint during CREATE DATABASE. Until 8.0.4
is out, you can protect yourself against this problem by doing a
CHECKPOINT command manually after CREATE DATABASE.
I'm not certain that this explains the other reports, although it well
may. The second complainant in particular didn't mention anything
about the problem being in a recently-created database.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2005-06-26 18:47:49 | Re: BUG #1727: Corrupt Zip file? |
Previous Message | Tom Lane | 2005-06-25 14:46:05 | Re: can't startup PG-8.0.3 |