Ben Roberts <benroberts@runtime-collective.com> writes:
> The scheduled maintenance script throws the following error:
> FATAL 2: open of /2/var/lib/postgres/data/pg_clog/0002 failed: No such file
> or directory
Could we see the results of ls -l /2/var/lib/postgres/data/pg_clog ?
It would seem that you have a tuple somewhere with a bogus transaction
number in it, which leads the tuple validity check code to try to access
a nonexistent segment of the transaction commit log (clog). It's hard
to say more without an idea of what reasonable transaction numbers are
in your installation; so the names and sizes of the files in the clog
directory are interesting ...
regards, tom lane
