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

2007-05-24 Thread Michael Nolan
On 5/24/07, Tom Lane <[EMAIL PROTECTED]> wrote: It sounds like you have a reproducible test case --- can you make it available to someone else? Not very easily, Tom. The tarball files are around 35 GB (uncompressed) and I assume they'd only work on a fairly similar system anyway. I assume s

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

2007-05-24 Thread Tom Lane
"Michael Nolan" <[EMAIL PROTECTED]> 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

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

2007-05-24 Thread Michael Nolan
Sorry, I meant 8.2.4 (darn typo virus) On 5/24/07, Michael Nolan <[EMAIL PROTECTED]> wrote: Recently I went through the steps to refresh the database (8.3.4) on my development server (running Fedora Core 5 Linux), making a tarball of the live database, then restoring it on the development serve

[GENERAL] Corrupted index file after restoring WAL on warm spare server

2007-05-24 Thread Michael Nolan
Recently I went through the steps to refresh the database (8.3.4) on my development server (running Fedora Core 5 Linux), making a tarball of the live database, then restoring it on the development server, and running all the archived WAL files. Everything worked fine as far as I can tell, I don'