Re: Postgres and --config-file option

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Aleksander Alekseev <aleksander(at)timescale(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Nathan Bossart <nathandbossart(at)gmail(dot)com>
Subject: Re: Postgres and --config-file option
Date: 2024-02-02 21:23:23
Message-ID: CAKFQuwaaCJ58HGcsKHvhsazJOtErk5ztmxpxkD52gdH-actBOg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jan 15, 2024 at 4:35 AM Aleksander Alekseev <
aleksander(at)timescale(dot)com> wrote:

> PFA the patch. It's short but I think it mitigates the problem.
>
>
I took a look at where these options are discussed in the documentation and
now feel that we should make these options clear more broadly (config and
libpq, plus pointing to --name from -c in a couple of places). It doesn't
add much verbosity and, frankly, if I was to pick one "--name=value" would
win and so I'd rather document it, leaving -c alone for historical reasons.

I've attached a replacement patch with the additional changes.

David J.

Attachment Content-Type Size
v2-0001-Clarify-error-message-about-specifying-config-fil.patch text/x-patch 6.1 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2024-02-02 21:27:54 Re: Postgres and --config-file option
Previous Message Robert Haas 2024-02-02 20:44:12 Re: pgbench - adding pl/pgsql versions of tests