Re: [PATCH] Identify LWLocks in tracepoints
От
Craig Ringer
Тема
Re: [PATCH] Identify LWLocks in tracepoints
Дата
Msg-id
CAGRY4nwaiPJc8wO0G7WZCgBmATC3GJVgvBoADZHDbCzhj8zTPw@mail.gmail.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 Wed, 5 May 2021 at 09:15, Craig Ringer wrote: >> warning: suggest braces around empty body in an ‘if’ statement [-Wempty-body] >> 1322 | TRACE_POSTGRESQL_LWLOCK_WAIT_START(T_NAME(lock), mode); >> | ^ > > Odd that I didn't get that. This compiler complaint is not due to the _ENABLED() test as such. It's due to the fact that we completely define out the TRACE_POSTGRESQL_ macros with src/backend/utils/Gen_dummy_probes.sed . While explicit braces could be added around each test, I suggest fixing Gen_dummy_probes.sed to emit the usual dummy statement instead. Patch attached.
В списке pgsql-hackers по дате отправления
От: Greg Nancarrow
Дата: