From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Bryan White" <bryan(at)arcamax(dot)com> |
Cc: | "pgsql-general" <pgsql-general(at)postgreSQL(dot)org> |
Subject: | Re: Corrupted Table |
Date: | 2000-07-31 22:49:38 |
Message-ID: | 19184.965083778@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Bryan White" <bryan(at)arcamax(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Herbert Liechti | 2000-07-31 22:50:27 | Re: postgres perl DBI |
Previous Message | Tom Lane | 2000-07-31 22:46:21 | Re: postgres access via perl failing after upgrade |