we need a special case when we are already a member of the MultiXact:
fall through without trying to reacquire the tuple lock.
Small implementation detail: Also keep a count of how many times the same session requested the same lock, and do not release the lock until he requests same number of releases.
Comments? Should we change HeapTupleSatisfiesUpdate's API to
distinguish this case, or is it better to have a localized change
in heap_lock_tuple?
--
gurjeet[.singh]@EnterpriseDB.com
singh.gurjeet@{ gmail | hotmail | yahoo }.com
