Bingo! Thanks Tom.
-----Original Message-----
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 22, 2004 11:33 AM
To: Dave Hartwig
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Can't Restart ver 8.0b3
"Dave Hartwig" <[EMAIL PROTECTED]> 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
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
