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

From Tom Lane
Subject Re: Transaction-scope advisory locks
Date
Msg-id 24631.1292338308@sss.pgh.pa.us
Whole thread Raw
In response to Re: Transaction-scope advisory locks  (Merlin Moncure <mmoncure@gmail.com>)
Responses Re: Transaction-scope advisory locks  (Andrew Dunstan <andrew@dunslane.net>)
Re: Transaction-scope advisory locks  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-hackers
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.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: SQL/MED - core functionality
Next
From: Andrew Dunstan
Date:
Subject: Re: Transaction-scope advisory locks