Postgres Pro
Downloads
Home   >   mailing lists

Re: strange behavior (corruption?) of large production database - Mailing list pgsql-hackers

From Tom Lane
Subject Re: strange behavior (corruption?) of large production database
Date
Msg-id 10027.1133569209@sss.pgh.pa.us
Whole thread Raw
In response to Re: strange behavior (corruption?) of large production  (Joe Conway <mail@joeconway.com>)
Responses Re: strange behavior (corruption?) of large production  (Joe Conway <mail@joeconway.com>)
List pgsql-hackers
Tree view 
Joe Conway <mail@joeconway.com> writes:
> Tom Lane wrote:
>> You could try a VACUUM FREEZE on pg_database though.

> Since this is a production machine, putting pg_filedump on it may be 
> problematic -- if I grovel through the bits by hand, can you give me a 
> hint about what to look for?

How about you copy off the pg_database file to someplace where it's OK
to run pg_filedump?  Doing that by hand is mighty tedious.

BTW, forget the "FREEZE" part, just VACUUM:
http://archives.postgresql.org/pgsql-general/2005-11/msg00097.php
        regards, tom lane

pgsql-hackers by date:

Previous
From: Joe Conway
Date:
Subject: Re: strange behavior (corruption?) of large production
Next
From: Philip Warner
Date:
Subject: Re: Optimizer oddness, possibly compounded in 8.1