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

From Josh Berkus
Subject Re: Transaction-scope advisory locks
Date
Msg-id 4D06D4B5.1000305@agliodbs.com
Whole thread Raw
In response to Re: Transaction-scope advisory locks  (Marko Tiikkaja <marko.tiikkaja@cs.helsinki.fi>)
List pgsql-hackers
> Oh, I forgot to mention.  The patch doesn't change any existing
> behaviour; the new behaviour can be invoked only by adding a new boolean
> argument:
> 
> SELECT pg_advisory_lock(1, false);
> 
> The lock space is the same though, but I don't feel strongly about it.

I could use this, and I think a lot more people would use advisory locks
with it.  Put it in the next CF and remind me to test it.

--                                  -- Josh Berkus                                    PostgreSQL Experts Inc.
                        http://www.pgexperts.com
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: hstores in pl/python
Next
From: Tom Lane
Date:
Subject: Re: Transaction-scope advisory locks