Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 76C6D2E004F for ; Wed, 20 Feb 2008 05:27:58 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 85180-03 for ; Wed, 20 Feb 2008 05:27:55 -0400 (AST) Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by postgresql.org (Postfix) with ESMTP id 70E0B2E0060 for ; Wed, 20 Feb 2008 05:27:55 -0400 (AST) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 4D7C291EAE for ; Wed, 20 Feb 2008 04:27:54 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Wed, 20 Feb 2008 04:27:54 -0500 X-Sasl-enc: ztTPg23o5tOW4uZbfLqPCE06EJ1v+lmTjwd79ulOlWDX 1203499673 Received: from [192.168.1.235] (76-191-150-176.dsl.dynamic.sonic.net [76.191.150.176]) by mail.messagingengine.com (Postfix) with ESMTP id CCFBA154C8 for ; Wed, 20 Feb 2008 04:27:53 -0500 (EST) Message-ID: <47BBF298.4010108@fastmail.net> Date: Wed, 20 Feb 2008 01:27:52 -0800 From: Darren Reed User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Power outage borked things (8.1.10)... Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200802/227 X-Sequence-Number: 28301 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