ok,
I fixed it using the dd command and the pg_dump is not complaining anymore,
but can I trust in my database now?
Thanks in advance!
----- Original Message -----
From: "Tom Lane" <tgl@sss.pgh.pa.us>
To: "Reimer" <carlosreimer@terra.com.br>
Cc: <pgsql-general@postgresql.org>
Sent: Friday, March 24, 2006 1:11 PM
Subject: Re: [GENERAL] URGENT! could not access status of transaction
> "Reimer" <carlosreimer@terra.com.br> writes:
>> pg_dump: ERROR: could not access status of transaction 1768711534
>> DETAIL: could not open file "/usr/local/pgsql/data/pg_clog/0696": =
>> Arquivo ou dire
>> t=F3rio n=E3o encontrado
>
>> How is the best way to fix? pg_resetxlog?
>
> resetxlog won't help: you've got corrupt data in that table. See the
> archives for previous threads about finding and removing corrupt rows.
>
> I concur with the nearby suggestion that you should be running something
> newer than 7.4.6, but even with an update you'll still be needing to
> clean up this corruption manually :-(
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>