| From: | Marko Tiikkaja <marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi> |
|---|---|
| To: | Szymon Guz <mabewlun(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Transaction-scope advisory locks |
| Date: | 2010-12-13 23:14:22 |
| Message-ID: | 4D06A8CE.9060601@cs.helsinki.fi |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2010-12-14 1:08 AM +0200, Szymon Guz wrote:
> On 13 December 2010 23:52, Marko Tiikkaja<marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi>wrote:
>> 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?
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.
Regards,
Marko Tiikkaja
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2010-12-13 23:45:29 | Re: Complier warnings on mingw gcc 4.5.0 |
| Previous Message | Szymon Guz | 2010-12-13 23:08:31 | Re: Transaction-scope advisory locks |