We recently had an issue where a misbehaving application was running a long transaction that modified a bunch of rows,
andthis was holding up other transactions that wanted to do similar modifications. No surprising there. But what I'm
unclearof is how this was showing up in pg_locks. The blocked transactions were all waiting on the transactionid of the
long-runningtransaction, not any particular relation or tuple. Why doesn't pg_locks show the actual blockage? Isn't
thatwhat MVCC is good for?
