Re: Corrupted Table - Mailing list pgsql-general

From Tom Lane
Subject Re: Corrupted Table
Date
Msg-id 19184.965083778@sss.pgh.pa.us
Whole thread Raw
In response to Re: Corrupted Table  ("Bryan White" <bryan@arcamax.com>)
List pgsql-general
"Bryan White" <bryan@arcamax.com> writes:
>> Shut down the postmaster and then copy the entire db (including pg_log
>> file) and it should work.  The catch is to make sure pg_log is in sync
>> with your table files.

> I would rather not leave my database down long enough to copy the entire db
> (3.5GB).

Well, you don't really need the *whole* db, just pg_log (and the other
tables at the top level of the data directory), the system tables
(pg_foo in the database subdir), and the table of interest.

> If not, how about if I first
> vacuum the table?

Don't do that --- it might wipe out vital clues.

            regards, tom lane

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: postgres access via perl failing after upgrade
Next
From: Herbert Liechti
Date:
Subject: Re: postgres perl DBI