Re: [PATCH] Identify LWLocks in tracepoints

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Craig Ringer <craig(dot)ringer(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] Identify LWLocks in tracepoints
Date: 2021-05-08 17:13:47
Message-ID: 241837.1620494027@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> writes:
> On 05.05.21 00:15, Andres Freund wrote:
>> I'm now getting
>> /home/andres/src/postgresql/src/backend/storage/lmgr/lwlock.c: In function ‘LWLockAcquire’:
>> /home/andres/src/postgresql/src/backend/storage/lmgr/lwlock.c:1322:58: warning: suggest braces around empty body in an ‘if’ statement [-Wempty-body]
>> 1322 | TRACE_POSTGRESQL_LWLOCK_WAIT_START(T_NAME(lock), mode);
>> | ^

> What compiler are you using in this situation?

All of these buildfarm members are now showing this warning:

calliphoridae gcc (Debian 10.1.0-6) 10.1.0
culicidae gcc (Debian 10.1.0-6) 10.1.0
flaviventris gcc (Debian 20200124-1) 10.0.1 20200124 (experimental)
francolin gcc (Debian 10.1.0-6) 10.1.0
piculetœ gcc (Debian 10.1.0-6) 10.1.0
rorqual gcc (Debian 10.1.0-6) 10.1.0
serinus gcc (Debian 20200124-1) 10.0.1 20200124 (experimental)
skink gcc (Debian 10.1.0-6) 10.1.0

so there's your answer.

(I wonder why flaviventris and serinus are still using an "experimental"
compiler version that is now behind mainstream.)

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2021-05-08 17:21:37 Re: plan with result cache is very slow when work_mem is not enough
Previous Message Noah Misch 2021-05-08 16:55:07 Re: Anti-critical-section assertion failure in mcxt.c reached by walsender