| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | "Froggy / Froggy Corp(dot)" <froggy(at)froggycorp(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Problem with a transaction on dump |
| Date: | 2007-04-04 14:51:18 |
| Message-ID: | 21664.1175698278@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Froggy / Froggy Corp. wrote:
>> pg_dump: ERREUR: Impossible d'accder au statut de la transaction
>> 892415538
> What files are there in main/pg_clog?
Doesn't really matter --- I'd say it's pretty obviously a data corruption
problem. That value equates to 35312e32 hex which looks way too much
like ASCII. Investigation with pg_filedump might give some clue about
what happened, but if you just want to salvage what you can, the key is
to identify and zero out the broken page. See past discussions of
recovery from data corruption in the archives.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Froggy / Froggy Corp. | 2007-04-04 14:51:57 | Re: Problem with a transaction on dump |
| Previous Message | Alvaro Herrera | 2007-04-04 14:38:39 | Re: Problem with a transaction on dump |