Re: Allowing printf("%m") only where it actually works

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Allowing printf("%m") only where it actually works
Date: 2018-08-12 07:27:31
Message-ID: alpine.DEB.2.21.1808120916590.6189@lancre
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Shay Rojansky 2018-08-12 07:51:28 Re: Stored procedures and out parameters
Previous Message Noah Misch 2018-08-12 06:48:15 Re: [HACKERS] Weaker shmem interlock w/o postmaster.pid