Re: pg_upgrade's exec_prog() coding improvement

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade's exec_prog() coding improvement
Date: 2012-08-25 04:52:09
Message-ID: 1345870329.21404.0.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 2012-08-24 at 10:08 -0400, Tom Lane wrote:
> Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
> > On 23.08.2012 23:07, Alvaro Herrera wrote:
> >> One problem with this is that I get this warning:
> >> /pgsql/source/HEAD/contrib/pg_upgrade/exec.c: In function ‘s_exec_prog’:
> >> /pgsql/source/HEAD/contrib/pg_upgrade/exec.c:96:2: warning: function might be possible candidate for ‘gnu_printf’ format attribute [-Wmissing-format-attribute]
> >> /pgsql/source/HEAD/contrib/pg_upgrade/exec.c:96:2: warning: function might be possible candidate for ‘gnu_printf’ format attribute [-Wmissing-format-attribute]
> >>
> >> I have no idea how to silence that. Ideas?
>
> > You can do what the warning suggests, and tell the compiler that
> > exec_prog takes printf-like arguments.
>
> exec_prog already has such decoration, and Alvaro's patch doesn't remove
> it. So the question is, exactly what the heck does that warning mean?

The warning is about s_exec_prog, not exec_prog.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2012-08-25 05:57:50 Re: plperl sigfpe reset can crash the server
Previous Message Tom Lane 2012-08-25 04:38:09 Re: plperl sigfpe reset can crash the server