pg_clog after crash

From: Andreas Schmitz <a(dot)schmitz(at)cityweb(dot)de>
To: pgsql-admin(at)postgresql(dot)org
Subject: pg_clog after crash
Date: 2004-06-11 11:46:36
Message-ID: 200406111346.36948.a.schmitz@cityweb.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin


Hello *,

after a harddisk filling up to a 100% the database crashed. This is the output
I get when I try to start the DB again. Is there any chance to get it back
running without using a dump ?

regards,

-Andreas

2004-06-11 13:38:23 [22379] LOG: database system was interrupted while in
recovery at 2004-06-11 13:32:44 CEST
HINT: This probably means that some data is corrupted and you will have to
use the last backup for recovery.
2004-06-11 13:38:23 [22379] LOG: checkpoint record is at 25/FB90EFA4
2004-06-11 13:38:23 [22379] LOG: redo record is at 25/FB90ED88; undo record
is at 0/0; shutdown FALSE
2004-06-11 13:38:23 [22379] LOG: next transaction ID: 10185227; next OID:
17088234
2004-06-11 13:38:23 [22379] LOG: database system was not properly shut down;
automatic recovery in progress
2004-06-11 13:38:23 [22379] LOG: redo starts at 25/FB90ED88
2004-06-11 13:38:24 [22379] PANIC: could not access status of transaction
10256385
DETAIL: could not read from file "/var/data/pgsql/data/dbs_1/pg_clog/0009" at
offset 204800: Success
2004-06-11 13:38:24 [22373] LOG: startup process (PID 22379) was terminated
by signal 6
2004-06-11 13:38:24 [22373] LOG: aborting startup due to startup process
failure

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Martin Marques 2004-06-11 11:48:49 Re: [GENERAL] out of memory error
Previous Message sathish 2004-06-11 09:44:07 doubt