"Gurjeet Singh" <singh.gurjeet@xxxxxxxxx> writes: > On 11/17/06, Tom Lane <tgl@xxxxxxxxxxxxx> wrote: >> 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. No need for that, because there isn't any heap_unlock_tuple. regards, tom lane
