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 C63D014B2A2E for ; Thu, 12 Aug 2004 01:22:13 -0300 (ADT) 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 52443-05 for ; Thu, 12 Aug 2004 04:22:05 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 3AFCA14B2A2B for ; Thu, 12 Aug 2004 01:22:03 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i7C4LxTq024308; Thu, 12 Aug 2004 00:21:59 -0400 (EDT) To: Drew Whittle Cc: pgsql-admin@postgresql.org Subject: Re: corrupt DB recovery In-reply-to: <1092280216.25843.28.camel@mcp> References: <1092280216.25843.28.camel@mcp> Comments: In-reply-to Drew Whittle message dated "12 Aug 2004 15:10:16 +1200" Date: Thu, 12 Aug 2004 00:21:58 -0400 Message-ID: <24307.1092284518@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200408/85 X-Sequence-Number: 14480 Drew Whittle writes: > I have two other db's that are 100% identical in everything but name and > data. (ie same structure etc), is it possible to use one of that data > files in them to over write the buggered file and fix the pg_proc error? You could try that, but unless the db's also have identical history (in the sense of the same set of transaction numbers that committed) it's unlikely to work. I think your problem is not that pg_class is buggered per se, so much as that you did not have correct pg_clog data to match it. The data files and the log files are an interlocking whole, you can't just plug in one part at random. > Any other suggestions that might get the data back or should I just > forget it and tell them to key it again? If you did extract something from this mess, how much could you trust it? Not a lot, because the bad-clog problem will affect visibility of rows in the user tables too. I'm afraid you're screwed :-(. Maybe you could learn something about proper backup procedures though. The backup you have obviously didn't work well --- how did you take it exactly? regards, tom lane