Re: releaseOk and LWLockWaitForVar - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: releaseOk and LWLockWaitForVar
Date
Msg-id 53A85860.2020400@vmware.com
Whole thread Raw
In response to Re: releaseOk and LWLockWaitForVar  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: releaseOk and LWLockWaitForVar  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On 06/23/2014 05:38 PM, Amit Kapila wrote:
> While looking at function LWLockWaitForVar(), espacially below
> code:
>
> TRACE_POSTGRESQL_LWLOCK_ACQUIRE(T_NAME(l), T_ID(l), LW_EXCLUSIVE);
>
> I think in this function tracing is done considering the Exclusive lock
> is acquired, however it might have granted access because of
> variable updation.  Basically this function's trace doesn't distinguish
> whether the access is granted due to the reason that there is no other
> exclusive locker or variable is updated.

Yeah. Not sure it's worth it to add new TRACE points for this, I'm not 
really familiar with the way the traces work or how people use them.

- Heikki




pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Atomics hardware support table & supported architectures
Next
From: Vik Fearing
Date:
Subject: Re: SQL access to database attributes