Re: Can't Restart ver 8.0b3

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Dave Hartwig" <daveh(at)Routescape(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Can't Restart ver 8.0b3
Date: 2004-12-22 16:32:41
Message-ID: 4484.1103733161@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Dave Hartwig" <daveh(at)Routescape(dot)com> writes:
> LOG: next transaction ID: 884736; next OID: 306834
> PANIC: could not access status of transaction 884736
> DETAIL: could not read from file
> "/usr/local/pgsql8b3/data/pg_clog/0000" at offset 221184: Success
> LOG: startup process (PID 17774) was terminated by signal 6
> LOG: aborting startup due to startup process failure

Hmm ... do we have a problem when the next XID is exactly at a page
boundary? I'll look into that.

> LOG: next transaction ID: 1048576; next OID: 306834
> PANIC: could not access status of transaction 1048576
> DETAIL: could not open file "/usr/local/pgsql8b3/data/pg_clog/0001": No
> such file or directory

IIRC, pg_resetxlog doesn't have any provision to create new pg_clog
segments. Which is probably an oversight, but it's easy enough to
do it by hand. Do something like
dd bs=8k count=1 </dev/zero >/usr/local/pgsql8b3/data/pg_clog/0001
and everything should be fine.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-12-22 16:34:50 Re: oldish libpq bug still in RC2
Previous Message Tom Lane 2004-12-22 16:25:42 Re: Thoughts about updateable views