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

From Andres Freund
Subject Re: Transaction-scope advisory locks
Date
Msg-id 201012141307.10147.andres@anarazel.de
Whole thread Raw
In response to Re: Transaction-scope advisory locks  (Marko Tiikkaja <marko.tiikkaja@cs.helsinki.fi>)
Responses Re: Transaction-scope advisory locks  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-hackers
On Tuesday 14 December 2010 00:14:22 Marko Tiikkaja wrote:
> The lock space is the same though, but I don't feel strongly about it.
I feel strongly that it needs the same locking space. I pretty frequently have 
the need for multiple clients trying to acquiring a lock in transaction scope 
(i.e. for accessing the cache) and one/few acquiring it in session scope (for 
building the cache).

Andres


pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: Transaction-scope advisory locks
Next
From: Peter Eisentraut
Date:
Subject: Re: hstores in pl/python