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 851B452861 for ; Thu, 16 Jun 2005 09:25:32 -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 30451-09 for ; Thu, 16 Jun 2005 12:25:30 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id F113F5283C for ; Thu, 16 Jun 2005 09:25:29 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j5GCPRga014341; Thu, 16 Jun 2005 08:25:27 -0400 (EDT) To: Simon Riggs Cc: "Bruno G. Albuquerque" , Scott Marlowe , pgsql-admin@postgresql.org Subject: Re: Indexes getting corrupted. In-reply-to: <1118912741.3645.206.camel@localhost.localdomain> References: <42A73B60.7010909@dba.com.br> <1118258780.5758.160.camel@state.g2switchworks.com> <42A9C2F7.50306@dba.com.br> <23641.1118422679@sss.pgh.pa.us> <1118912741.3645.206.camel@localhost.localdomain> Comments: In-reply-to Simon Riggs message dated "Thu, 16 Jun 2005 10:05:41 +0100" Date: Thu, 16 Jun 2005 08:25:27 -0400 Message-ID: <14340.1118924727@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.005 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200506/111 X-Sequence-Number: 17866 Simon Riggs writes: > I'm suspicious of a more subtle intermittent error. Yeah, I am too, but so far none of the reporters have been cooperative about providing more information :-( > We have no > information about what the magic values are, only that they are not > correct. Should we increase the information returned for that error? I think the proposed patch is a waste of time. What I am hoping to get from people is a dump of the whole first page of the corrupted index (via pg_filedump, or even good ol' od). That might give us some idea of what we are dealing with --- localized corruption in a basically good metapage, or wholesale replacement of the page with some other page (and if so what), or maybe it is a hardware fault after all. You can't draw those sorts of conclusions from one or two words, but with a whole page to look at you have a shot at telling the difference. regards, tom lane