Re: Corrupted index file after restoring WAL on warm spare server - Mailing list pgsql-general

From Tom Lane
Subject Re: Corrupted index file after restoring WAL on warm spare server
Date
Msg-id 20079.1180036593@sss.pgh.pa.us
Whole thread Raw
In response to Corrupted index file after restoring WAL on warm spare server  ("Michael Nolan" <htfoot@gmail.com>)
Responses Re: Corrupted index file after restoring WAL on warm spare server
List pgsql-general
"Michael Nolan" <htfoot@gmail.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

pgsql-general by date:

Previous
From: "A.M."
Date:
Subject: Re: why postgresql over other RDBMS
Next
From: Alvaro Herrera
Date:
Subject: Re: why postgresql over other RDBMS