| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Wim Goedertier <Wim_Goedertier(at)symantec(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: recover as much as possible (xlog flush request not satisfied) |
| Date: | 2012-07-09 14:07:05 |
| Message-ID: | 21295.1341842825@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Wim Goedertier <Wim_Goedertier(at)symantec(dot)com> writes:
> After studying http://www.postgresql.org/docs/8.2/static/app-pgresetxlog.html
> I ran:
> su <db-user> -c 'pg_resetxlog -f -x 0x9A00000 -m 0x10000 -O 0x10000 -l 0x1,0xB67,0x58 <PGDATA-directory>'
> and yes, it worked perfectly!
> After that I could pg_dump, drop database, create database and import the dump.
> Now, I'm verifying the consistency on the level of my application.
Great! But a word of warning: personally, I'd have re-initdb'd the
whole installation. When you have a problem like this, there's no good
reason to assume that only the active database is broken.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steven Schlansker | 2012-07-09 17:35:21 | Re: Suboptimal query plan fixed by replacing OR with UNION |
| Previous Message | Wim Goedertier | 2012-07-09 13:02:08 | Re: recover as much as possible (xlog flush request not satisfied) |