Re: Corrupted index file after restoring WAL on warm spare server

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Michael Nolan" <htfoot(at)gmail(dot)com>
Cc: "pgsql general" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Corrupted index file after restoring WAL on warm spare server
Date: 2007-05-24 19:56:33
Message-ID: 20079.1180036593@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Michael Nolan" <htfoot(at)gmail(dot)com> writes:
> Howevever, when I go to access one table, the index appears to be corrupted
> because the record I get for one query doesn't match the record key I give.

> Reindexing that table on the warm spare system fixes the problem.

> I redid setting up the warm spare server a second time to see if it was a
> one-time anomaly, but I have the exact same condition again.

> What could be causing this? If this is a bug, what can I do to help track
> it down?

It sounds like you have a reproducible test case --- can you make it
available to someone else?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alvaro Herrera 2007-05-24 19:57:16 Re: why postgresql over other RDBMS
Previous Message Michael Nolan 2007-05-24 19:36:29 Re: Corrupted index file after restoring WAL on warm spare server