Re: Transaction-scope advisory locks
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Merlin Moncure <mmoncure@gmail.com>
Cc: Andres Freund <andres@anarazel.de>, pgsql-hackers@postgresql.org, Marko Tiikkaja <marko.tiikkaja@cs.helsinki.fi>, Szymon Guz <mabewlun@gmail.com>
Date: 2010-12-14T14:51:48Z
Lists: 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