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.1808120916590.6189@lancre
Whole thread Raw
In response to Re: Allowing printf("%m") only where it actually works  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Allowing printf("%m") only where it actually works
List pgsql-hackers
> [...]
>
> At this point I'm inclined to give up and revert 3a60c8ff8.  It's not
> clear that we can really make the warning situation better, as opposed
> to just moving the warnings from one platform to another.

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.

A revert would help.

-- 
Fabien.


pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: [HACKERS] Weaker shmem interlock w/o postmaster.pid
Next
From: Shay Rojansky
Date:
Subject: Re: Stored procedures and out parameters