Alvaro Herrera wrote:
> Please *note the behavior change* of HeapTupleSatisfiesUpdate: it will
> now return HeapTupleBeingUpdated when a tuple is locked by an Xid that's
> a subtransaction of the current top transactionn. That case previously
> returned HeapTupleBeingUpdated. If someone wants to say that we
> shouldn't change that in 9.3, please speak up. But do note that it was
> already returning that valu ewhen the lock was a multixact, so the new
> behavior can be said to be more consistent.
I hate to keep replying to myself, but above I intended to say "that
case previously returned HeapTupleMayBeUpdated".
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
