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 7079F5E3639 for ; Fri, 27 Aug 2004 01:06:27 -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 33735-07 for ; Fri, 27 Aug 2004 04:06:30 +0000 (GMT) Received: from aibo.runbox.com (aibo.runbox.com [193.71.199.94]) by svr1.postgresql.org (Postfix) with ESMTP id EB2EB5E3631 for ; Fri, 27 Aug 2004 01:06:21 -0300 (ADT) Received: from [10.9.9.64] (helo=gaspode.runbox.com) by bolivar.runbox.com with esmtp (Exim 4.24) id 1C0Y0P-0002jg-5H; Fri, 27 Aug 2004 06:06:25 +0200 Received: from [221.242.208.180] (helo=[192.168.0.3]) by gaspode.runbox.com with asmtp (uid:182597) (Exim 4.24) id 1C0Y0O-0005QG-IM; Fri, 27 Aug 2004 06:06:24 +0200 Message-ID: <412EB2AF.1080502@andrewfarmer.com> Date: Fri, 27 Aug 2004 13:03:59 +0900 From: Andrew Farmer User-Agent: Mozilla Thunderbird 0.6 (X11/20040729) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane Cc: pgsql-admin@postgresql.org Subject: Re: 7.3.4 Table corruption References: <412BEE3D.8070409@andrewfarmer.com> <10928.1093485410@sss.pgh.pa.us> In-Reply-To: <10928.1093485410@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Sender: 182597 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/287 X-Sequence-Number: 14682 Thanks for the advice. I'll relax the constraints on the table, and reload that table from the dump, might take a while to fix any problems, but it should be safer. Regards, Andrew Tom Lane wrote: >Andrew Farmer writes: > > >>My question is, if I load the good dump into a clean database, and then >>find the underlying file that represents the broken table and copy it >>over the top of the broken table, am I likely to face any big problems? >> >> > >This strikes me as a real good way to shoot yourself in the foot ;-). >Better take a backup and be prepared to restore from it. And I'd >suggest experimenting in a scratch installation before you try it for >real. > >Having said that, I think it would work, if your "clean database" is >another DB in the same cluster (you could *not* copy from data prepared >under a different postmaster). And you'll need to copy all the indexes >on that table, and its toast table and toast table index if it has one. >And shut down the postmaster while you do the copying. > > regards, tom lane > >---------------------------(end of broadcast)--------------------------- >TIP 4: Don't 'kill -9' the postmaster > > >