Re: Postgres and --config-file option

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Michael Paquier <michael(at)paquier(dot)xyz>, Aleksander Alekseev <aleksander(at)timescale(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Subject: Re: Postgres and --config-file option
Date: 2024-05-15 09:49:22
Message-ID: c201585e-39cd-442f-b2dc-7cb7da1008d1@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 15.05.24 04:07, Michael Paquier wrote:
> Not sure that these additions in --help or the docs are necessary.
> The rest looks OK.
>
> - "You must specify the --config-file or -D invocation "
> + "You must specify the --config-file (or equivalent -c) or -D invocation "
>
> How about "You must specify the --config-file, -c
> \"config_file=VALUE\" or -D invocation"? There is some practice for
> --opt=VALUE in .po files.

Yeah, some of this is becoming quite unwieldy, if we document and
mention each spelling variant of each option everywhere.

Maybe if the original problem is that the option --config-file is not
explicitly in the --help output, let's add it to the --help output?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bharath Rupireddy 2024-05-15 09:59:47 Re: Introduce new multi insert Table AM and improve performance of various SQL commands with it for Heap AM
Previous Message Peter Eisentraut 2024-05-15 09:39:47 Re: SQL:2011 application time