X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 585DA52A6F for ; Fri, 1 Apr 2005 12:52:13 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 82033-05 for ; Fri, 1 Apr 2005 11:52:03 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.191]) by svr1.postgresql.org (Postfix) with ESMTP id 107A152A64 for ; Fri, 1 Apr 2005 12:52:02 +0100 (BST) Received: from [212.227.126.202] (helo=mrvnet.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1DHKh1-000563-00; Fri, 01 Apr 2005 13:52:03 +0200 Received: from [172.23.4.147] (helo=config20.kundenserver.de) by mrvnet.kundenserver.de with esmtp (Exim 3.35 #1) id 1DHKh0-0002ev-00; Fri, 01 Apr 2005 13:52:02 +0200 Received: from www-data by config20.kundenserver.de with local (Exim 3.35 #1 (Debian)) id 1DHKh0-0000hk-00; Fri, 01 Apr 2005 13:52:02 +0200 To: =?iso-8859-1?Q? "L=2EBoldareva" ?= Subject: =?iso-8859-1?Q?Re:__How_to_recover_when_can't_start_database?= From: Cc: Message-Id: <28292295$1112355374424d322e5958c4.20461539@config20.schlund.de> X-Binford: 6100 (more power) X-Originating-From: 28292295 X-Mailer: Webmail X-Routing: UK X-Received: from config20 by 62.231.149.155 with HTTP id 28292295 for pg@pierro.dds.nl; Fri, 1 Apr 2005 13:50:02 +0200 Content-Type: text/plain; charset="iso-8859-1" Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Priority: 3 Date: Fri, 1 Apr 2005 13:50:02 +0200 X-Provags-ID: kundenserver.de abuse@kundenserver.de ident:@172.23.4.147 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.414 tagged_above=0 required=5 tests=AWL, NO_REAL_NAME X-Spam-Level: X-Archive-Number: 200504/10 X-Sequence-Number: 17023 "L.Boldareva" wrote on 01.04.2005, 12:02:21: > Hi! > (Hope this is the right place to post) > > I crashed the postmaster and cannot start it anymore, with the error > > LOG: database system was interrupted while in recovery at 2005-04-01 11:04:33 CEST > 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 5/6F00C540 > LOG: redo record is at 5/6F000ABC; undo record is at 0/0; shutdown FALSE > LOG: next transaction ID: 599824; next OID: 147679259 > LOG: database system was not properly shut down; automatic recovery in > progress > LOG: redo starts at 5/6F000ABC > PANIC: btree_split_redo: lost left sibling > LOG: startup process (PID 5603) was terminated by signal 6 > LOG: aborting startup due to startup process failure > > Is there a way to recover from that? > > I don't have a fresh backup, but loosing some couple of days won't be a > problem. > > I use PG 8.0 on a linux box, with standard postgresq.conf (except some > increased memory settings). > Well, it *might* be possible to recover using a Point in Time Recovery, with some manipulation. Never been done, as far as I know, so don't hold your breath. PITR wasn't designed for the situation where you haven't actually taken a backup, but it might still be possible. I think it will cause a problem since there's no pg_stop_backup() been executed, but perhaps we can think of a way to override that or build a custom recovery server. First, backup exactly everything you have now and save it. You might even want to do it twice, so there's no mistake. If you've got the original failure log that would be great. We need to establish what time the original failure took place, if there was one, so we can try to rollforward to a time just before that. Anyway, I'll be free in a few hours to have a look at this, but it could take a few days to figure it out, so don't promise anybody success and don't say it would be quick either. You may not wish to wait that long, I've no idea of your business. Please save the database anyway so we've got a test case. Best Regards, Simon Riggs