Re: [PATCH] Identify LWLocks in tracepoints

Поиск
Список
Период
Сортировка
Искать
От
Peter Eisentraut
Тема
Re: [PATCH] Identify LWLocks in tracepoints
Дата
Msg-id
0b6e2998-b4b0-a60e-0847-9792690709fd@enterprisedb.com
Ответ на
Re: [PATCH] Identify LWLocks in tracepoints (Craig Ringer)
Список
Дерево обсуждения
[PATCH] Identify LWLocks in tracepoints Craig Ringer <craig.ringer@enterprisedb.com>
Re: [PATCH] Identify LWLocks in tracepoints Dmitry Dolgov <9erthalion6@gmail.com>
Re: [PATCH] Identify LWLocks in tracepoints Craig Ringer <craig.ringer@enterprisedb.com>
Re: [PATCH] Identify LWLocks in tracepoints Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: [PATCH] Identify LWLocks in tracepoints Craig Ringer <craig.ringer@enterprisedb.com>
Re: [PATCH] Identify LWLocks in tracepoints Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: [PATCH] Identify LWLocks in tracepoints Masahiko Sawada <sawada.mshk@gmail.com>
Re: [PATCH] Identify LWLocks in tracepoints Craig Ringer <craig.ringer@enterprisedb.com>
Re: [PATCH] Identify LWLocks in tracepoints Craig Ringer <craig.ringer@enterprisedb.com> 
On 2021-01-14 09:39, Craig Ringer wrote:
> On Thu, 14 Jan 2021 at 15:56, Peter Eisentraut 
>  > wrote:
> 
>     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.
> 
> 
> I'm certain it's a copy/paste bug.

I have committed that patch.
В списке pgsql-hackers по дате отправления
Предыдущее
От: Bharath Rupireddy
Дата:
Следующее
От: Chengxi Sun
Дата:
FAQ