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 EB174528AD for ; Fri, 22 Jul 2005 10:49:31 -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 89984-02 for ; Fri, 22 Jul 2005 13:49:26 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id D95E25289C for ; Fri, 22 Jul 2005 10:49:25 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.13.1/8.13.1) with ESMTP id j6MDnPEU091245 for ; Fri, 22 Jul 2005 13:49:25 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.13.1/8.13.1/Submit) id j6MDevZn089250 for pgsql-admin@postgresql.org; Fri, 22 Jul 2005 13:40:57 GMT (envelope-from news) From: "Eric Comeau" X-Newsgroups: pgsql.admin Subject: Corrupt table, is zero_damaged_pages available in v7.2? Date: Fri, 22 Jul 2005 09:41:00 -0400 Organization: Signiant Lines: 15 Message-ID: X-Complaints-To: usenet@news.hub.org X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.2180 X-RFC2646: Format=Flowed; Original X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Archive-Number: 200507/190 X-Sequence-Number: 18246 We have "one" corrupted table in a v7.2.4 database. The others are good. We have identified the table should have 25 rows in it, and using pg_dump we can get the first 10. I was wondering if we could use the zero_damaged_pages under v7.2 to hopefully skip over the corrupted data and read the remaining records. Is this parameter only available in v7.3+? I am in the process of getting a source build tree together to build pg_filedump hopefully. Thanks - Eric