pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruno G. Albuquerque <balbuquerque@dba.com.br>
To: pgsql-admin@postgresql.org
Subject: Re: Indexes getting corrupted.
Date: Thu, 16 Jun 2005 10:20:28 -0300
Message-ID: <42B17C9C.5030506@dba.com.br> (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>


Tom Lane wrote:
>>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 :-(

Well, at least from me, I can tell you I gave all information I came up 
with. One thing that I pointed out is this (Windows 2000):

When you shutdown the machine just after you run my customized 
installation procedure and you check the log after rebooting, you will 
notice that only the first message (saying that a fast shutdown request 
was received) will be in the log. The other messages that mention the 
shutdown process completed succesfully do not appear. If I check the 
database, the indexes *WILL* be corrupt.

I solved it by automatically stopping the server after the installation 
precedure concludes. This solves this problem and, even after rebooting, 
the indexes seems to be ok.

> 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.

I can try to revert my changes to get the problem to happen again. Just 
tell me what exactly you need me to do. Also, this problem happened on 
*SEVERAL* machines with different configurations. Actually, it happened 
with all machines I tried and the "fix" I implemented (as mentioned 
above) worked on all of them too.

-Bruno

**********************************************************************
Informação transmitida destina-se apenas à pessoa a quem foi endereçada e pode conter informação confidencial, legalmente protegida e para conhecimento exclusivo do destinatário. Se o leitor desta advertência não for o seu destinatário, fica ciente de que sua leitura, divulgação ou cópia é estritamente proibida. Caso a mensagem tenha sido recebida por engano, favor comunicar ao remetente e apagar o texto de qualquer computador.


The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information, by person or entity other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.
**********************************************************************



view thread (9+ messages)  latest in thread

Message-ID: <42B17C9C.5030506@dba.com.br>
Permalink:  ../42B17C9C.5030506@dba.com.br/
Also on:    postgresql.org/message-id/42B17C9C.5030506@dba.com.br

 · 

reply

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: balbuquerque@dba.com.br
  Subject: Re: Indexes getting corrupted.
  In-Reply-To: <42B17C9C.5030506@dba.com.br>
  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> <42B17C9C.5030506@dba.com.br>

* 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