Power outage borked things (8.1.10)...
От | Darren Reed |
---|---|
Тема | Power outage borked things (8.1.10)... |
Дата | |
Msg-id | 47BBF298.4010108@fastmail.net обсуждение исходный текст |
Ответы |
Re: Power outage borked things (8.1.10)...
|
Список | pgsql-admin |
Starting up postgres, I get the log contents below. Is it really as bad as it suggests, namely that I need to recover from backup? The pg_clog directory has the following: # ls -al pg_clog/ total 1216 drwx------ 2 postgres wheel 512 Jan 17 09:09 ./ drwx------ 10 postgres wheel 512 Feb 20 00:44 ../ -rw------- 1 postgres wheel 253952 Dec 8 11:09 0000 -rw------- 1 postgres wheel 253952 Dec 19 17:29 0001 -rw------- 1 postgres wheel 253952 Jan 2 17:49 0002 -rw------- 1 postgres wheel 253952 Jan 16 10:19 0003 -rw------- 1 postgres wheel 90112 Jan 22 15:34 0004 The error seems to suggest that it is at EOF... Darren LOG: startup process (PID 765) was terminated by signal 6 LOG: aborting startup due to startup process failure LOG: database system was interrupted while in recovery at 2008-02-20 00:44:08 PST HINT: This probably means that some data is corrupted and you will have to use the last backup for recovery. LOG: checkpoint record is at 2/64507F8C LOG: redo record is at 2/64507F8C; undo record is at 0/0; shutdown FALSE LOG: next transaction ID: 4570963; next OID: 24576 LOG: next MultiXactId: 1; next MultiXactOffset: 0 LOG: database system was not properly shut down; automatic recovery in progress LOG: redo starts at 2/64507FD0 PANIC: could not access status of transaction 4570965 DETAIL: could not read from file "pg_clog/0004" at offset 90112: Undefined error: 0 LOG: startup process (PID 306) was terminated by signal 6 LOG: aborting startup due to startup process failure
В списке pgsql-admin по дате отправления: