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

From Robert Haas
Subject Re: Transaction-scope advisory locks
Date
Msg-id AANLkTinbJLUYBiNv8k-MXMinwVK7T5RE06UYzyQzUJQZ@mail.gmail.com
Whole thread Raw
In response to Re: Transaction-scope advisory locks  (Marko Tiikkaja <marko.tiikkaja@cs.helsinki.fi>)
Responses Re: Transaction-scope advisory locks  (Marko Tiikkaja <marko.tiikkaja@cs.helsinki.fi>)
List pgsql-hackers
On Thu, Jan 20, 2011 at 5:22 AM, Marko Tiikkaja
<marko.tiikkaja@cs.helsinki.fi> wrote:
> On 2011-01-17 9:28 AM +0200, Itagaki Takahiro wrote:
>>
>> Here is a short review for Transaction scoped advisory locks:
>> https://commitfest.postgresql.org/action/patch_view?id=518
>
> Thanks for reviewing!
>
>> == Features ==
>> The patch adds pg_[try_]advisory_xact_lock[_shared] functions.
>> The function names follows the past discussion -- it's better than
>> "bool isXact" argument or changing the existing behavior.
>>
>> == Coding ==
>> I expect documentation will come soon.
>
> I'm sorry about this, I have been occupied with other stuff.  I'm going to
> work on this tonight.

Any update on this?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: sepgsql contrib module
Next
From: Tom Lane
Date:
Subject: Re: auto-sizing wal_buffers