Received: from maia.hub.org (unknown [200.46.208.211])
	by mail.postgresql.org (Postfix) with ESMTP id 6BC3F634763
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Tue,  2 Feb 2010 16:30:29 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia,
	port 10024) with ESMTP id 83914-02-3
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Tue,  2 Feb 2010 20:30:06 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by mail.postgresql.org (Postfix) with ESMTP id DA77D65A1EF
	for <pgsql-admin@postgresql.org>; Tue,  2 Feb 2010 15:55:52 -0400 (AST)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id o12JqdEf029453;
	Tue, 2 Feb 2010 14:52:39 -0500 (EST)
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
In-reply-to: 
 <FA20D4C4FEBFD148B1C0CB09913825FC01EBD52C6C@XCH-SW-06V.sw.nos.boeing.com>
References: 
 <FA20D4C4FEBFD148B1C0CB09913825FC01EBD52C6C@XCH-SW-06V.sw.nos.boeing.com>
Comments: In-reply-to "Wang, Mary Y" <mary.y.wang@boeing.com>
	message dated "Tue, 02 Feb 2010 08:55:14 -0800"
Date: Tue, 02 Feb 2010 14:52:39 -0500
Message-ID: <29452.1265140359@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-2.465 tagged_above=-10 required=5 tests=AWL=0.134,
	BAYES_00=-2.599
X-Spam-Level: 
X-Archive-Number: 201002/22
X-Sequence-Number: 33625

"Wang, Mary Y" <mary.y.wang@boeing.com> writes:
> I'm having a bad day. My Postgresql has this error "FATAL 2:  XLogFlush: request is not satisfied".   I tried to follow the instructions from a thread about looking for a core dump, but when I tried to start the postmaster, I got "/usr/bin/postmaster: Startup proc 30595 exited with status 512 - abort".

You've got a corrupted page that is affected by a WAL replay operation,
so things are pretty much a mess.

> I'm pg version is postgresql-7.1.3-2.  What are my options?

[ blanches... ]  You do realize that that version has been obsolete
since 2002?

pg_resetxlog was a contrib module in 7.1, so if you can find the
software repository you got postgresql from, you should be able to
install postgresql-contrib.  However, I am betting this thing is so
old that you don't even have the chance at doing that.

Most likely you're going to have to go back to your last backup.
After which, you should make it a priority to get onto a less
antique version of Postgres (and the underlying OS too, no doubt).

			regards, tom lane