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 -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin