X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 76DE2D1D458 for ; Fri, 21 Nov 2003 06:21:16 +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 03049-03 for ; Fri, 21 Nov 2003 02:20:46 -0400 (AST) Received: from dmhi.ct.ro (dmhi.ct.ro [193.226.151.66]) by svr1.postgresql.org (Postfix) with ESMTP id E7D17D1D247 for ; Fri, 21 Nov 2003 02:20:36 -0400 (AST) Received: from [192.168.2.114] (helo=aaa) by dmhi.ct.ro with smtp (Exim 3.03 #1) id 1AN6VU-0003aL-00 for pgsql-sql@postgresql.org; Fri, 21 Nov 2003 10:19:12 +0200 Message-ID: <003e01c3aff7$8475c740$7202a8c0@aaa> From: "cristi" To: References: <004801c3acfc$c6b395e0$7201a8c0@aaa> <1036.1069301945@sss.pgh.pa.us> Subject: Re: FATAL 2: PageIndexTupleDelete Date: Fri, 21 Nov 2003 08:20:10 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/254 X-Sequence-Number: 16069 Yes, you right! I used pg_dump command and now is working. Thank you very much! PS. I have version 7.2.2 on RH 8.0 > > FATAL 2: PageIndexTupleDelete: corrupted page pointers: lower =3D 12289, up= > > per =3D > > 1, special =3D 60672 > > > Why do I have this error message and how can I fix it? > > This is a data-corruption problem. Have you had any system crashes or > other odd behavior lately? > > As far as recovering, you can probably fix the broken index with > REINDEX, if the corruption doesn't extend further than the index that's > being complained of. Otherwise you might have to resort to a dump and > reload. > > You should also think about updating your Postgres installation. You > didn't say what version you're running (naughty naughty, that's required > info in any trouble report) but I can tell from the spelling of the > error message that it's not a current release. > > regards, tom lane >