| From: | Keaton Adams <kadams(at)mxlogic(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Any way to bring up a PG instance with corrupted data in it? |
| Date: | 2009-06-08 19:30:50 |
| Message-ID: | C652C30A.BF3C%kadams@mxlogic.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I had to calculate out the next transaction ID and -f (force) the change, but once I did this the DB came back up. So, thanks for the info, and now I know how this works.
The plan now is to dump the databases and reload them to ensure overall database integrity.
Thanks for the reply,
Keaton
On 6/8/09 11:46 AM, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
Keaton Adams <kadams(at)mxlogic(dot)com> writes:
> This is a QA system and unfortunately there is no recent backup.... So as a last resort I am looking for any way to bring up Postgres when it has corrupt data in it:
pg_resetxlog?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2009-06-08 20:30:05 | Re: NOT NULL with CREATE TYPE |
| Previous Message | Oliver Kohll - Mailing Lists | 2009-06-08 19:08:02 | Re: [pgsql-general] Daily digest v1.9081 (14 messages) |