| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Restoring fscked up postgres 7.1 |
| Date: | 2005-01-21 16:37:15 |
| Message-ID: | 87651qagck.fsf@stark.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
Kristaps Armanis <krisha(at)grafton(dot)lv> writes:
> Is there any solution?
I think what you have to do is use pg_resetxlog with -x and a value just shy
of 2^32. then pg_dump and restore into a fresh database. I've never done it
though so perhaps you should wait until someone with more experience speaks
up. I would also suggest taking a cold backup of the bad database before
running pg_resetxlog.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Korotun | 2005-01-22 15:23:21 | Shared memory seems not in use |
| Previous Message | Pallav Kalva | 2005-01-21 16:15:25 | Postgres 8.0 Log Configuration |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jackson Pauls | 2005-01-21 16:39:32 | Re: connecting with a 8.0.0 client with ssl |
| Previous Message | Mário Gamito | 2005-01-21 16:27:58 | static pgadmin |