From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
cc: pgsql-hackers@lists.postgresql.org
Subject: Re: Bugs in ecpg's macro mechanism
In-reply-to: <20240416010544.tsupdybl752vywkw@awork3.anarazel.de>
References: <998011.1713217712@sss.pgh.pa.us>
 <20240415231044.fjjibtnwcypowzni@awork3.anarazel.de>
 <1063578.1713228436@sss.pgh.pa.us>
 <20240416010544.tsupdybl752vywkw@awork3.anarazel.de>
Comments: In-reply-to Andres Freund <andres@anarazel.de>
	message dated "Mon, 15 Apr 2024 18:05:44 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1071979.1713231214.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 15 Apr 2024 21:33:34 -0400
Message-ID: <1071980.1713231214@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1071980.1713231214%40sss.pgh.pa.us>
Precedence: bulk

Andres Freund <andres@anarazel.de> writes:
> On 2024-04-15 20:47:16 -0400, Tom Lane wrote:
>> Ah, thanks.  I guess this depends on getopt_long reordering arguments
>> (since the "-o outfile" bit will come later).  That is safe enough
>> in HEAD since 411b72034, but it might fail on weird platforms in v16.
>> How much do we care about that?  (We can avoid that hazard in the
>> makefile build easily enough.)

> As moving the arguments around would just be the following, I see no rea=
son to
> just do so.

Fair enough.  I'm inclined to include that change only in v16, though.

			regards, tom lane