| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Wahl, Steven" <stevenwa(at)aiinet(dot)com> |
| Cc: | "'pgsql-admin(at)postgresql(dot)org'" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Cannot start the PostgreSQL v7.1.3 database |
| Date: | 2002-10-04 18:14:23 |
| Message-ID: | 25272.1033755263@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
"Wahl, Steven" <stevenwa(at)aiinet(dot)com> writes:
> DEBUG: redo starts at (2, 899933184)
> DEBUG: ReadRecord: record with zero len at (2, 923216960) DEBUG: redo done
> at (2, 923216920)
> FATAL 2: XLogFlush: request is not satisfied
> Is the database corrupt? Can it be saved?
Yes, and probably. I'd suggest running contrib/pg_resetxlog, then doing
a prompt pg_dumpall, after which you can initdb and reload the dump.
You should check your data for corruption, in the form of
partially-applied recent transactions. There may be actual garbage
in there too --- the error suggests that the LSN pointer in some data
page is garbage, which may mean that more of that page has been
clobbered as well.
As long as you have to dump and reload anyway, this would be a real
good time to update to PG 7.2.3.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Sullivan | 2002-10-04 19:06:51 | Re: idle in transaction with mod_perl |
| Previous Message | Chris Miles | 2002-10-04 18:05:28 | PostgreSQL and 2-node failover cluster solutions |