Re: Transaction-scope advisory locks - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Transaction-scope advisory locks
Date
Msg-id 14807.1292346328@sss.pgh.pa.us
Whole thread Raw
In response to Re: Transaction-scope advisory locks  (Marko Tiikkaja <marko.tiikkaja@cs.helsinki.fi>)
Responses Re: Transaction-scope advisory locks  (Marko Tiikkaja <marko.tiikkaja@cs.helsinki.fi>)
List pgsql-hackers
Marko Tiikkaja <marko.tiikkaja@cs.helsinki.fi> writes:
> On 2010-12-14 4:23 AM +0200, Tom Lane wrote:
>> Uh, I don't think so.  It sure looks like you have changed the user
>> lockmethod to be transactional, ie, auto-release on commit/abort.

> I was under the impression that passing sessionLock=true to 
> LockAcquire(), combined with allLocks=false to LockReleaseAll() would be 
> enough to prevent that from happening.  My tests seem to agree with this.

> Am I missing something?

All the places that look at LockMethodData->transactional ?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: hstores in pl/python
Next
From: Jeff Janes
Date:
Subject: Re: BufFreelistLock