ERROR: could not access status of transaction

I recently saw this in some postgres logs:

ERROR: could not access status of transaction ...
DETAIL: could not open file "pg_clog/...": No such file or directory
STATEMENT: COPY ...

The copy command was issued amongst a number of other queries from an
application layer at the same time as a pg_dumpall was running.

Based on this:

http://archives.postgresql.org/pgsql-committers/2006-01/msg00287.php

I would not have thought this cluster was vulnerable. It's running
8.1.3. It makes me a little nervous that the nightly backup was
interrupted, but it makes me a little more nervous that it seems
indicative of an abstruse error condition. Any thoughts from the
hackers?

--
Thomas F. O'Connell
Database Architecture and Programming
Sitening, LLC

http://www.sitening.com/
3004 B Poston Avenue
Nashville, TN 37203-1314
615-260-0005 (cell)
615-469-5150 (office)
615-469-5151 (fax)