From: Tom Lane <tgl@sss.pgh.pa.us>
To: Simon Riggs <simon@2ndquadrant.com>
Cc: Bruno G. Albuquerque <balbuquerque@dba.com.br>
Cc: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Indexes getting corrupted.
Date: Thu, 16 Jun 2005 08:25:27 -0400
Message-ID: <14340.1118924727@sss.pgh.pa.us> (raw)
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>
Simon Riggs <simon@2ndquadrant.com> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, simon@2ndquadrant.com, balbuquerque@dba.com.br, smarlowe@g2switchworks.com
Subject: Re: Indexes getting corrupted.
In-Reply-To: <14340.1118924727@sss.pgh.pa.us>
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> <14340.1118924727@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox