| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Bugs in ecpg's macro mechanism |
| Date: | 2024-04-16 01:33:34 |
| Message-ID: | 1071980.1713231214@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)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 reason to
> just do so.
Fair enough. I'm inclined to include that change only in v16, though.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-04-16 01:35:53 | Re: Differential code coverage between 16 and HEAD |
| Previous Message | David Rowley | 2024-04-16 01:30:01 | Add memory context type to pg_backend_memory_contexts view |