Re: initdb: introduce PG_CMD_PRINTF intestead of PG_CMD_PRINTF{1,2,3}

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alexander Kuleshov <kuleshovmail(at)gmail(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: initdb: introduce PG_CMD_PRINTF intestead of PG_CMD_PRINTF{1,2,3}
Date: 2016-03-17 13:20:47
Message-ID: 25069.1458220847@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alexander Kuleshov <kuleshovmail(at)gmail(dot)com> writes:
> The src/bin/initdb/initdb.c provides three macros to write data to
> cmdfd. All of these macro do the same, but with different amount of
> arguments for fprintf().

> Attached patch introduces PG_CMD_PRINTF macro which will take set of
> variadic arguments via __VA_ARGS__ to replace the PG_CMD_PRINTF{1,2,3}
> macros.

> Any objections?

Yes. We do not accept patches that don't work on compilers without
__VA_ARGS__ (cf 7b077af50 for a recent example). At some point there
might be a reason that's compelling enough to make us move that
portability goalpost, but this hardly seems like such a reason.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-03-17 13:35:50 Re: typmod is always -1
Previous Message Michael Paquier 2016-03-17 13:20:14 Re: [HACKERS] pgbench -C -M prepared gives an error