| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | "Hackers (PostgreSQL)" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: strange behavior (corruption?) of large production database |
| Date: | 2005-12-03 00:20:09 |
| Message-ID: | 10027.1133569209@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Joe Conway <mail(at)joeconway(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Philip Warner | 2005-12-03 00:35:04 | Re: Optimizer oddness, possibly compounded in 8.1 |
| Previous Message | Joe Conway | 2005-12-03 00:17:23 | Re: strange behavior (corruption?) of large production |