Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id EA6DF9F9B1B for ; Sun, 7 Oct 2007 22:48:22 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 90034-06 for ; Sun, 7 Oct 2007 22:48:08 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 7E35E9F9DFC for ; Sun, 7 Oct 2007 22:48:19 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l981mGGc026144; Sun, 7 Oct 2007 21:48:16 -0400 (EDT) To: "Mike C" cc: pgsql-admin@postgresql.org Subject: Re: Database Recovery In-reply-to: References: Comments: In-reply-to "Mike C" message dated "Mon, 08 Oct 2007 10:47:49 +1300" Date: Sun, 07 Oct 2007 21:48:16 -0400 Message-ID: <26143.1191808096@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/42 X-Sequence-Number: 26956 "Mike C" writes: > I have a corrupt database. I copied the database directory offsite and > restored from a backup. I'm now trying to recover data in the corrupt > database added since the last backup. Any advice on how to approach > this? If you're lucky, REINDEX might solve your problems. The messages you showed are all about index corruption, which REINDEX can fix. If you've got corruption in the tables themselves then you might be screwed, but try reindexing and see what happens ... regards, tom lane