Postgres Pro
Downloads
Home   >   mailing lists

Re: [PATCH] Identify LWLocks in tracepoints - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [PATCH] Identify LWLocks in tracepoints
Date
Msg-id 2afc78a8-54c0-6d31-d022-f8c0e3dfc36f@enterprisedb.com
Whole thread Raw
In response to [PATCH] Identify LWLocks in tracepoints  (Craig Ringer <craig.ringer@enterprisedb.com>)
Responses Re: [PATCH] Identify LWLocks in tracepoints  (Craig Ringer <craig.ringer@enterprisedb.com>)
List pgsql-hackers
Tree view 
On 2020-12-19 06:00, Craig Ringer wrote:
> Patch 1 fixes a bogus tracepoint where an lwlock__acquire event would be 
> fired from LWLockWaitForVar, despite that function never actually 
> acquiring the lock.

This was added in 68a2e52bbaf when LWLockWaitForVar() was first 
introduced.  It looks like a mistake to me too, but maybe Heikki wants 
to comment.

pgsql-hackers by date:

Previous
From: Sergey Shinderuk
Date:
Subject: Re: pg_preadv() and pg_pwritev()
Next
From: Michael Paquier
Date:
Subject: Re: Improper use about DatumGetInt32