Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 68D47633729 for ; Thu, 22 Apr 2010 13:51:38 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 26839-03-7 for ; Thu, 22 Apr 2010 16:51:26 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 0F90E637123 for ; Thu, 22 Apr 2010 11:42:37 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id o3MEgXB8000672; Thu, 22 Apr 2010 10:42:33 -0400 (EDT) To: Achilleas Mantzios cc: "pgsql-admin@postgresql.org" Subject: Re: pgsql 8.3.3 "Invalid page header" leads to "FATAL: segment too big" In-reply-to: <201004221516.08729.achill@matrix.gatewaynet.com> References: <201004221516.08729.achill@matrix.gatewaynet.com> Comments: In-reply-to Achilleas Mantzios message dated "Thu, 22 Apr 2010 14:16:08 +0200" Date: Thu, 22 Apr 2010 10:42:33 -0400 Message-ID: <671.1271947353@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.108 tagged_above=-10 required=5 tests=AWL=-0.198, BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201004/304 X-Sequence-Number: 34398 Achilleas Mantzios writes: > Then i did: (as i said i do not need the contents of msgsource - yet the contents of msgno are vital) > dd if=/dev/zero of=/usr/local/var/lib/pgsql/data/base/125714957/125716013 seek=672720 bs=8192 count=1 > However, after that, unfortunately i get constant postgresql server restarts with: > FATAL: segment too big You got the dd command wrong and made the file size change to something it shouldn't be. I think you can use dd to truncate the file back to what it should be (ie, exactly 1GB) but haven't had enough caffeine to remember exactly how. I think the underlying error is that block 672720 isn't going to be in the first segment of the table --- you need to be zeroing something in one of the other segments... regards, tom lane