"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
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
In response to
pgsql-general by date
|Next:||From: Herbert Liechti||Date: 2000-07-31 22:50:27|
|Subject: Re: postgres perl DBI|
|Previous:||From: Tom Lane||Date: 2000-07-31 22:46:21|
|Subject: Re: postgres access via perl failing after upgrade |