pg_clog after crash

Поиск
Список
Период
Сортировка
От Andreas Schmitz
Тема pg_clog after crash
Дата
Msg-id 200406111346.36948.a.schmitz@cityweb.de
обсуждение исходный текст
Ответы Re: pg_clog after crash  (Tom Lane <tgl@sss.pgh.pa.us>)
Список 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



В списке pgsql-admin по дате отправления:

Предыдущее
От: "lise chhay"
Дата:
Сообщение: how to test the server webauth on mandrake
Следующее
От: Martin Marques
Дата:
Сообщение: Re: [GENERAL] out of memory error