Greg Stark <gsstark@xxxxxxx> writes: > Excluding the cases where our own xid is in the tuple I think the > relevant cases are either > xmin aborted or in progress (or in future) > MOVED_OFF and xvac committed > MOVED_IN and xvac aborted or is in progress (or in future) Ah. I hadn't bothered to check the code in detail before asking about the current XID. Given subsequent data, it seems that current XID must have moved past xvac while we were wondering about it. This could mean either corrupted xvac values, or that the crash caused current XID to go backwards (suggesting loss of both the current pg_control and a big chunk of WAL). Since multiple tuples on different pages were involved, I'm inclined to believe the second theory. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
