From: Tom Lane <tgl@sss.pgh.pa.us>
To: Wang, Mary Y <mary.y.wang@boeing.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Startup proc 30595 exited with status 512 - abort and FATAL 2: XLogFlush
Date: Tue, 02 Feb 2010 15:14:25 -0500
Message-ID: <29816.1265141665@sss.pgh.pa.us> (raw)
In-Reply-To: <FA20D4C4FEBFD148B1C0CB09913825FC01EBD52D8E@XCH-SW-06V.sw.nos.boeing.com>
References: <FA20D4C4FEBFD148B1C0CB09913825FC01EBD52C6C@XCH-SW-06V.sw.nos.boeing.com>
<29452.1265140359@sss.pgh.pa.us>
<FA20D4C4FEBFD148B1C0CB09913825FC01EBD52D8E@XCH-SW-06V.sw.nos.boeing.com>
"Wang, Mary Y" <mary.y.wang@boeing.com> writes:
> Thanks for the help
> I was able to find pg_resetxlog in the path. Are there any precautions that I need to be aware of? Or I just don't have any choice?
I'd suggest taking a tarball copy of the $PGDATA tree, so you can at
least get back to where you were if it doesn't work.
Actually ... is this RHEL 2.1 as I suspect? If so, can you find the
last RHEL 2.1 update, which was postgresql-7.1.3-7.rhel2.1AS?
There was a fix in that that might well address your issue:
* Wed Feb 23 2005 Tom Lane <tgl@redhat.com> 7.1.3-7.rhel2.1AS
- Back-patch community 7.2 change in error recovery behavior of XLogFlush;
this allows successful restart of the database even in the presence of
dubious values in LSN fields of database pages.
Alternatively, if you have the ability to rebuild the version you've
got, you're welcome to try adding the patch, which is attached.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, mary.y.wang@boeing.com
Subject: Re: Startup proc 30595 exited with status 512 - abort and FATAL 2: XLogFlush
In-Reply-To: <29816.1265141665@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox