Turns out this was most likely the pg_upgrade bug. In our case, I was able
to dump and recreate the table in question. Since then, this has been made
public: http://wiki.postgresql.org/wiki/20110408pg_upgrade_fix
--
View this message in context: http://postgresql.1045698.n5.nabble.com/could-not-access-status-of-transaction-1118722281-tp4283137p4293709.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.