Re: cache lookup failed for index

[Nathan Robertson <nathan.robertson@xxxxxxxxx>]

There was a cascade effect. Apache failed which caused the server overall to fail. The data is stored on an iSCSI drive and the mount of the iSCSI drive became corrupt when everything failed. I was able to remount the drive and get access to data now I have this index error.

So, this is where I'm at. If anyone could help resolve the index cache error I would be eternally great full.

On Wed, Jun 30, 2010 at 9:36 AM, Kevin Grittner <Kevin.Grittner@xxxxxxxxxxxx> wrote:

Nathan Robertson <nathan.robertson@xxxxxxxxx> wrote:

> Apache failed which caused PSQL to fail which at some point caused
> some data in the database to become corrupt.

What?  What does Apache have to do with psql (a command-line client
for PostgreSQL), and how would either of those failing cause a
database corruption?  Could you give more details?  Did the OS lock
up at some point?  Was there any power loss while PostgreSQL was
running?

Without an event like that, database corruption is often the result
of hardware problems.  Testing your RAM and making sure you have
SMART monitoring working on the drives, with due attention to any
reported problems, might be a good idea; otherwise, whatever you
recover may be further damaged.

Also, it would help a lot to know what your postgresql.conf file
contains (excluding all comments).

But first and foremost, you should make a file-copy backup of your
entire PostgreSQL data directory tree with the PostgreSQL server
stopped, if you haven't done that already.  Any attempt at recovery
may misfire, and you might want to get back to what you have now.

-Kevin