Tom, thank you for your help. I increased 000E to 81920 and the databse is working now. We are using RHAS 3.0 and it does have /dev/zero.
Dan. -----Original Message----- From: Tom Lane [mailto:[EMAIL PROTECTED] Sent: Thursday, June 24, 2004 12:34 PM To: Shea,Dan [CIS] Cc: [EMAIL PROTECTED] Subject: Re: [PERFORM] after using pg_resetxlog, db lost "Shea,Dan [CIS]" <[EMAIL PROTECTED]> writes: > I determined the largest was 12,293,162 and set it to > pg_resetxlog -x 15000000 /var/lib/pgsql/data Okay, but it looks like you will also need to adjust pg_clog to cover that transaction ID range. (I had thought pg_resetxlog would handle this for you, but it looks like not.) > Jun 24 15:02:05 murphy postgres[28061]: [11-1] PANIC: could not access status of > transaction 15000030 > Jun 24 15:02:05 murphy postgres[28061]: [11-2] DETAIL: could not read from file > "/var/lib/pgsql/data/pg_clog/000E" at offset 73728: Success You need to append zeroes (8K at a time) to /var/lib/pgsql/data/pg_clog/000E until it's longer than 73728 bytes. I'd use something like dd bs=8k count=1 </dev/zero >>/var/lib/pgsql/data/pg_clog/000E assuming that your system has /dev/zero. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
