Re: Corrupted Table - Mailing list pgsql-general

From Bryan White
Subject Re: Corrupted Table
Date
Msg-id 026401bffb37$80d24460$2dd260d1@arcamax.com
Whole thread Raw
In response to Corrupted Table  ("Bryan White" <bryan@arcamax.com>)
Responses Re: Corrupted Table  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
> 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).  I have control over when changes are applied to this table.  If I
restart the database and make certain no updates/inserts/deletes occur then
will all info be flushed from the pg_log file?  If not, how about if I first
vacuum the table?




pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Corrupted Table
Next
From: "Fetter, David M"
Date:
Subject: postgres perl DBI