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

From Marko Tiikkaja
Subject Re: Transaction-scope advisory locks
Date
Msg-id 4D497738.2070803@cs.helsinki.fi
Whole thread Raw
In response to Re: Transaction-scope advisory locks  (Marko Tiikkaja <marko.tiikkaja@cs.helsinki.fi>)
Responses Re: Transaction-scope advisory locks  (Itagaki Takahiro <itagaki.takahiro@gmail.com>)
List pgsql-hackers
On 2011-01-28 10:12 AM +0200, I wrote:
> I still didn't
> address the issue with pg_advisory_unlock_all() releasing transaction
> scoped locks, but I'm going to.

.. and here's the patch.  I'm not too confident with the code I added to
storage/lmgr/lock.c, but it seems to be working.

Earlier there was some discussion about adding regression tests for
advisory locks.  However, I don't see where they would fit in our
current .sql files and adding a new one just for a few tests didn't seem
right.  Anyone have an idea where they should go or should I just add a
new one?


Regards,
Marko Tiikkaja

Attachment

pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: ALTER EXTENSION UPGRADE, v3
Next
From: Anssi Kääriäinen
Date:
Subject: REVIEW: alter extension upgrade (patch v3)