Re: src/port/getopt_long.c lossy with arguments having no option characters

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: src/port/getopt_long.c lossy with arguments having no option characters
Date: 2015-04-03 14:08:27
Message-ID: 28931.1428070107@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Michael Paquier <michael(dot)paquier(at)gmail(dot)com> writes:
> The implementation of getopt_long in src/port has some limitations,
> for example such commands do not work but they should:

No, those should not work. You're too used to versions that don't insist
on switches-before-non-switch-arguments. Such behavior is an extension
that is not standard, is not documented in any Postgres documentation,
and tends to have bad corner-case behaviors. I don't feel a need to make
our implementation replicate that.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Eisentraut 2015-04-03 19:47:38 Re: src/port/getopt_long.c lossy with arguments having no option characters
Previous Message Ilya Bazylchuk 2015-04-03 11:14:37 Postgresql 9.4.1 stuck all queries when making multi updates