Re: Transaction-scope advisory locks

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Marko Tiikkaja <marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi>, Szymon Guz <mabewlun(at)gmail(dot)com>
Subject: Re: Transaction-scope advisory locks
Date: 2010-12-14 12:07:09
Message-ID: 201012141307.10147.andres@anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2010-12-14 12:09:58 Re: hstores in pl/python
Previous Message Dimitri Fontaine 2010-12-14 10:52:25 Re: Transaction-scope advisory locks