Re: Allowing printf("%m") only where it actually works - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: Allowing printf("%m") only where it actually works
Date
Msg-id alpine.DEB.2.21.1808122229320.8536@lancre
Whole thread Raw
In response to Re: Allowing printf("%m") only where it actually works  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
>> Indeed, there are hundreds of warnings around "pg_printf_attribute_m"
>> added with gcc 7.3.0 on by ubuntu 18.04 laptop, thanks to 3a60c8ff.
>
> Oh?  What warnings exactly?  I would not expect any new warnings except
> on platforms where gcc believes the local printf is non POSIX compliant,
> which certainly ought not happen on any non-obsolete Linux.

Hmmm. Strange. The good news, is sthat it does not show anymore. Maybe 
this was because I had not done a "configure" before recompiling. Sorry 
for the noise.

-- 
Fabien.


pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Explain buffers wrong counter with parallel plans
Next
From: Toshi Harada
Date:
Subject: "WIP: Data at rest encryption" patch and, PostgreSQL 11-beta3