pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Anjan Dave <adave@vantage.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: pg_clog corrupt, can't start postgres
Date: Mon, 21 Feb 2005 11:42:06 -0500
Message-ID: <632.1109004126@sss.pgh.pa.us> (raw)
In-Reply-To: <4BAFBB6B9CC46F41B2AD7D9F4BBAF78509881E@vt-pe2550-001.vantage.vantage.com>
References: <4BAFBB6B9CC46F41B2AD7D9F4BBAF78509881E@vt-pe2550-001.vantage.vantage.com>

"Anjan Dave" <adave@vantage.com> writes:
> The partition ran out of space from an import process. I cleared up the space and attempted to start the postgres service again, but it doesn't start and i get following in the message log.
> PANIC:  could not access status of transaction 45514755
> DETAIL:  could not read from file "/var/lib/pgsql/data/pg_clog/002B" at offset 106496: Success
> LOG:  startup process (PID 23991) was terminated by signal 6
> LOG:  aborting startup due to startup process failure

> Postgres is 7.4.1 on this machine.
 
> I saw some previous posts on this subject and so far the solution seems to be initialize and restore databases from the dumps.

Before that, try updating to 7.4.7 (or at least 7.4.2) --- this looks
like the same bug fixed here:

2004-01-26 14:16  tgl

	* src/backend/access/transam/varsup.c (REL7_4_STABLE): Repair
	incorrect order of operations in GetNewTransactionId().  We must
	complete ExtendCLOG() before advancing nextXid, so that if that
	routine fails, the next incoming transaction will try it again. 
	Per trouble report from Christopher Kings-Lynne.

You might also go back to the mail list archives from that time and see
what advice was given to Chris about getting out of the problem he found
himself in.  I *think* that something along the line of forcibly
appending a page of zeroes to that clog file might be the best solution,
but this was more than a year ago and I don't recall for sure.

			regards, tom lane



view thread (4+ messages)  latest in thread

Message-ID: <632.1109004126@sss.pgh.pa.us>
Permalink:  ../632.1109004126@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/632.1109004126@sss.pgh.pa.us

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, adave@vantage.com
  Subject: Re: pg_clog corrupt, can't start postgres
  In-Reply-To: <632.1109004126@sss.pgh.pa.us>
  References: <4BAFBB6B9CC46F41B2AD7D9F4BBAF78509881E@vt-pe2550-001.vantage.vantage.com> <632.1109004126@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