Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Matthias Hörmann <matthias(dot)hoermann(at)saltation(dot)com>
Cc: Daniel Gustafsson <daniel(at)yesql(dot)se>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
Date: 2025-09-03 14:57:53
Message-ID: 804476.1756911473@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Matthias =?utf-8?Q?H=C3=B6rmann?= <matthias(dot)hoermann(at)saltation(dot)com> writes:
> The 2025-09-03 13:45:15, Daniel Gustafsson wrote:
>> This is the intended behaviour, --help (and --version) is parsed specially and
>> must be the first parameter. We do this for all command line utilities.

> Well, the use-case that comes up quite often for me (for any commands,
> not just postgres) is that I add parameters I know or remember from my
> last look at --help and then want to check again what else to add, for
> that it is useful to be able to use --help as the last parameter.

FWIW, I agree with this. While I don't try to do that with PG
utilities (since I know it doesn't work), I frequently rely on that
behavior of our configure script. I'd be in favor of recognizing
--help (though probably not -?) in any argument position. Less sure
about --version.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2025-09-03 15:35:26 Re: BUG #19040: Memory leak in hashed subplan node due to missing hashtempcxt reset
Previous Message Tom Lane 2025-09-03 14:48:17 Re: BUG #18960: Mistake in test test_simple_pipeline (libpq_pipeline.c)