Re: Transaction-scope advisory locks

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Marko Tiikkaja <marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi>
Cc: Szymon Guz <mabewlun(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Transaction-scope advisory locks
Date: 2010-12-14 17:05:28
Message-ID: 14807.1292346328@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Marko Tiikkaja <marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi> writes:
> On 2010-12-14 4:23 AM +0200, Tom Lane wrote:
>> Uh, I don't think so. It sure looks like you have changed the user
>> lockmethod to be transactional, ie, auto-release on commit/abort.

> I was under the impression that passing sessionLock=true to
> LockAcquire(), combined with allLocks=false to LockReleaseAll() would be
> enough to prevent that from happening. My tests seem to agree with this.

> Am I missing something?

All the places that look at LockMethodData->transactional ?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2010-12-14 17:05:31 Re: hstores in pl/python
Previous Message Tom Lane 2010-12-14 17:01:30 Re: Re: Proposed Windows-specific change: Enable crash dumps (like core files)