Re: [PATCH] Identify LWLocks in tracepoints

Поиск
Список
Период
Сортировка
От Craig Ringer
Тема Re: [PATCH] Identify LWLocks in tracepoints
Дата
Msg-id CAGRY4nwEcS56yCwz6F-kW6Z6vo=xHNdXjqNDq4vQETf3tA6QSg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [PATCH] Identify LWLocks in tracepoints  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Ответы Re: [PATCH] Identify LWLocks in tracepoints  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Список pgsql-hackers
Дерево обсуждения
On Thu, 14 Jan 2021 at 15:56, Peter Eisentraut <peter.eisentraut@enterprisedb.com> 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.

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Craig Ringer
Дата:
Сообщение: Re: [PATCH] Identify LWLocks in tracepoints
Следующее
От: "tsunakawa.takay@fujitsu.com"
Дата:
Сообщение: [bug fix] Fix the size calculation for shmem TOC