From: Simon Riggs <simon@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bruno G. Albuquerque <balbuquerque@dba.com.br>
Cc: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: pgsql-admin@postgresql.org, David Parker <dparker@tazznetworks.com>
Subject: Re: Indexes getting corrupted.
Date: Fri, 17 Jun 2005 22:37:19 +0100
Message-ID: <1119044239.3645.234.camel@localhost.localdomain> (raw)
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>
On Thu, 2005-06-16 at 08:25 -0400, Tom Lane wrote:
> 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.
Sorry, let me explain. I immediately assumed that all problem reporters
had not provided further information because they could not, not because
they would not.
The patch is trivial and your suggested methods of looking into this are
much preferable. However, that relies on somebody being able to locate
the metapage, even assuming they don't overwrite the whole thing and
continue. The bug is intermittent and so re-running will allow work to
continue, so it would seem that is exactly what they do.
My patch would allow some more information to be retrieved in the
meantime, while we hope for somebody to upload a damaged metapage. If
the patch is not sufficient, then I'd suggest that the metapage be
dumped to log so it can be more easily provided for inspection.
In general, such matters are usually hardware faults. But all reporters
of this error in 8.0 have only reported index errors and no others,
which leads me to suspect a software related cause.
Best Regards, Simon Riggs
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: simon@2ndquadrant.com, tgl@sss.pgh.pa.us, balbuquerque@dba.com.br, smarlowe@g2switchworks.com, dparker@tazznetworks.com
Subject: Re: Indexes getting corrupted.
In-Reply-To: <1119044239.3645.234.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> <14340.1118924727@sss.pgh.pa.us> <1119044239.3645.234.camel@localhost.localdomain>
* 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