| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Andre Lucas <andre(at)amazoniasistemas(dot)com(dot)br>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: PSQL Help |
| Date: | 2020-02-18 04:37:37 |
| Message-ID: | 20200218043737.GG4176@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Feb 17, 2020 at 10:39:16PM -0500, Tom Lane wrote:
> FWIW, Andres' example *will* work on some platforms, because glibc's
> getopt_long() takes it upon itself to rearrange the arguments.
> But it doesn't work everywhere, which is why we only document/recommend
> the stricter argument order.
This is actually the case of our fallback implementation used for
example on Windows with MSVC builds. This led to fixes in our
regression tests like c67a86f, so we avoid this style as much as
possible on portability's ground.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laxminarayan, Sudhanva | 2020-02-18 06:32:38 | Not able to run query/scripts on our Postgre instance which is on cloud foundry |
| Previous Message | Hazuki Amamiya | 2020-02-18 03:48:49 | Re: Possible memory leak in PostgreSQL 12.2 on truncate, insert or delete when type interval is involved |