Re: Transaction-scope advisory locks
Marko Tiikkaja <marko.tiikkaja@cs.helsinki.fi>
From: Marko Tiikkaja <marko.tiikkaja@cs.helsinki.fi>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Itagaki Takahiro <itagaki.takahiro@gmail.com>,
pgsql-hackers@postgresql.org
Date: 2011-01-21T17:18:33Z
Lists: pgsql-hackers
On 1/20/2011 7:35 AM, Tom Lane wrote: > Marko Tiikkaja<marko.tiikkaja@cs.helsinki.fi> writes: >> This seems useful, since the xact lock would be automatically released >> if an error happens during "-- do something here" so you wouldn't need >> to worry about releasing the lock elsewhere. But I'm not sure this is >> safe. Can anyone see a problem with it? > > I think the POLA dictates that the behavior of that should be that you > now have both a transactional and a nontransactional hold on the lock; > and only the transactional hold goes away at commit. Yes, I believe that's what happens now. But I guess you answered my question too by not pointing out a huge flaw in that thinking. Regards, Marko Tiikkaja