X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id E326F9DC84D for ; Fri, 24 Mar 2006 11:28:33 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 44675-08 for ; Fri, 24 Mar 2006 11:28:38 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 836739DC83F for ; Fri, 24 Mar 2006 11:28:31 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k2OFSafW004819; Fri, 24 Mar 2006 10:28:36 -0500 (EST) To: =?ISO-8859-2?Q?R=F3zsahegyi_L=E1szl=F3?= cc: pgsql-admin@postgresql.org Subject: Re: Invalid page feader on Solaris 10 In-reply-to: <20060324090324.bbc620c2.laszlo.rozsahegyi@rool.hu> References: <20060324090324.bbc620c2.laszlo.rozsahegyi@rool.hu> Comments: In-reply-to =?ISO-8859-2?Q?R=F3zsahegyi_L=E1szl=F3?= message dated "Fri, 24 Mar 2006 09:03:24 +0100" Date: Fri, 24 Mar 2006 10:28:36 -0500 Message-ID: <4818.1143214116@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.114 required=5 tests=[AWL=0.114] X-Spam-Score: 0.114 X-Spam-Level: X-Archive-Number: 200603/236 X-Sequence-Number: 20993 =?ISO-8859-2?Q?R=F3zsahegyi_L=E1szl=F3?= writes: > The dump of my database is about 2 GB if we are lucky. > If not, we have one of error messages: > - pg_dump: ERROR: invalid memory alloc request size 2623204397 > - pg_dump: ERROR: could not access status of transaction 2423378468 > DETAIL: could not open file "pg_clog/0907": No such file or directory > - pg_dump: ERROR: invalid page header in block 16147 of relation "jn_szll" > What is the problem? All of those look like corrupt-data symptoms to me. I wonder whether you've got hardware problems (flaky disk, flaky memory, bad cable ...) How repeatable are the errors? Do they always occur for just one table, or is the problem widespread? regards, tom lane