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

From Andrew Dunstan
Subject Re: Transaction-scope advisory locks
Date
Msg-id 4D078637.90000@dunslane.net
Whole thread Raw
In response to Re: Transaction-scope advisory locks  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

On 12/14/2010 09:51 AM, Tom Lane wrote:
> Merlin Moncure<mmoncure@gmail.com>  writes:
>> Not that I'm necessarily against the proposal, but what does this do
>> that can't already be done by locking a table or a table's row?
> I agree with Andres' point about this: sometimes it'd be more convenient
> for an advisory lock to be released automatically at transaction end.
> If you have a mix of clients that want that behavior with others that
> want a persistent hold on the same locks, you can't do it with regular
> locks.
>

Right. And that's why they need to be in the same lockspace.

cheers

andrew


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Transaction-scope advisory locks
Next
From: Tom Lane
Date:
Subject: Re: SQL/MED - core functionality