From: | Szymon Guz <mabewlun(at)gmail(dot)com> |
---|---|
To: | Marko Tiikkaja <marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Transaction-scope advisory locks |
Date: | 2010-12-13 23:08:31 |
Message-ID: | AANLkTi=wK4aqnN7a9+i6C+PNq_hf74jFY184j3mauwmp@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 13 December 2010 23:52, Marko Tiikkaja <marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi>wrote:
> Hi,
>
> I often find myself wanting advisory locks that are automatically released
> when the transaction ends, so here's a small patch trying to do just that.
> I don't know much about the lock system so the patch is in the state "it
> looks like this would work". Any comments on the technical details are
> welcome. There's obviously a lot of documentation and READMEs to change
> too, but I thought I'd see what people think about the idea before going
> there.
>
> So, thoughts?
>
>
>
In my opinion changing current behavior is not a good idea. I know some
software that relies on current behavior and this would break it. Maybe add
that as an option, or add another type of advisory lock?
regards
Szymon
From | Date | Subject | |
---|---|---|---|
Next Message | Marko Tiikkaja | 2010-12-13 23:14:22 | Re: Transaction-scope advisory locks |
Previous Message | Marko Tiikkaja | 2010-12-13 22:52:28 | Transaction-scope advisory locks |