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 A0E02D1B1FD for ; Thu, 22 Jul 2004 14:28:24 -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 57563-03 for ; Thu, 22 Jul 2004 17:28:13 +0000 (GMT) Received: from dnsmail.rentrak.com (mtx1.rentrak.com [208.26.192.5]) by svr1.postgresql.org (Postfix) with ESMTP id CCB02D1B1DC for ; Thu, 22 Jul 2004 14:28:12 -0300 (ADT) Received: from rtk_mail_1.rentrak.com (rtkmail1.rentrak.com [208.26.192.2]) by dnsmail.rentrak.com (Postfix) with ESMTP id E4B242999D for ; Thu, 22 Jul 2004 10:26:28 -0700 (PDT) Received: from [97.0.177.64] (rtknat.rentrak.com [208.26.192.4]) by rtk_mail_1.rentrak.com; Thu, 22 Jul 2004 10:28:04 -0700 Message-ID: <40FFF98C.3000309@rentrak.com> Date: Thu, 22 Jul 2004 10:29:48 -0700 From: Ian Burrell User-Agent: Mozilla Thunderbird 0.6 (X11/20040519) X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Invalid page header Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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: 200407/250 X-Sequence-Number: 14318 I get the following error message when doing a select on a table: ERROR: invalid page header in block 295 of relation "reported_titles" I found some messages that said this means a block of this table is corrupt. I found some suspicious lines in the server log just before: ERROR: could not access status of transaction 3651584 DETAIL: could not open file "/usr/local/pgsql/data/pg_clog/0003": No such file or directory How do I fix this corruption? I have dumped as much of the databases as I can including about half of this table. Only this table is corrupt. What could cause the corruption? We are using custom C code. Could bugs in this be causing it? Or is hardware problems more likely? - Ian