X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id BAB64D1D1CD for ; Tue, 17 Feb 2004 23:45:09 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 94760-07 for ; Tue, 17 Feb 2004 19:45:10 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 5BF18D1CB1D for ; Tue, 17 Feb 2004 19:45:07 -0400 (AST) 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 i1HNj4LB018919; Tue, 17 Feb 2004 18:45:04 -0500 (EST) To: Michael Adler Cc: pgsql-admin@postgresql.org Subject: Re: how to recover corrupt data In-reply-to: <20040217153101.GB25887@pobox.com> References: <20040217153101.GB25887@pobox.com> Comments: In-reply-to Michael Adler message dated "Tue, 17 Feb 2004 10:31:01 -0500" Date: Tue, 17 Feb 2004 18:45:03 -0500 Message-ID: <18918.1077061503@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/263 X-Sequence-Number: 12437 Michael Adler writes: > Is there any way to extract this (possibly intact) data? It looks like you have one corrupted, perhaps partially zeroed, page in your table. There may be more, but the trace output you show only has corrupted tuples on one page (11193). You could try replacing that page with zeroes, which will lose the rows on that page but allow you to recover the rest of the data. See the archives for discussion of corruption recovery procedures (searching for references to pg_filedump will probably lead you to the right threads). regards, tom lane