"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
> ERROR: could not access status of transaction 4244329
> DETAIL: could not open file "/usr/local/pgsql/data/pg_clog/0004": No
> existe el fichero o el directorio
What files actually appear in /usr/local/pgsql/data/pg_clog/ ?
The standard advice for working around this sort of thing is to create a
dummy pg_clog/0004 file and fill it with 256K of zeroes, so that the
VACUUM will decide that the affected row is dead. However it would be
a good idea to first try to understand what's gone wrong. Is this an
isolated dropped-bit in a transaction status field, or a symptom of more
general corruption in the table? You could try to determine which page
of the table contains the corrupted row, and then dump out that page
with pg_filedump for visual analysis. (See past discussions of
corrupted-data recovery in the list archives for details.)
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
