From: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, Peter Eisentraut <peter(at)eisentraut(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-20 09:20:02 |
Message-ID: | CAJ7c6TPbHmVRQ=wGOBfZVVWJJ9OZ2gROW-ShTLxVrgpGJ1pP8w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> > If the reason that somebody is upset is because it's not technically
> > true to say that you *must* do one of those things, we could fix that
> > with "You must" -> "You can" or with "You must specify" -> "Specify".
> > The patch you propose is also not terrible or anything, but it goes in
> > the direction of listing every alternative, which will become
> > unpalatable as soon as somebody adds one more way to do it, or maybe
> > it's unpalatable already.
>
> I agree that it's not necessary or particularly useful for this hint
> to be exhaustive. I could get behind your suggestion of
> s/You must specify/Specify/, but I also think it's fine to do nothing.
Fair enough, let's leave the help message as is then. I closed the
corresponding CF entry.
--
Best regards,
Aleksander Alekseev
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Cave-Ayland | 2024-05-20 09:20:09 | Re: commitfest.postgresql.org is no longer fit for purpose |
Previous Message | Mark Cave-Ayland | 2024-05-20 09:19:05 | Re: commitfest.postgresql.org is no longer fit for purpose |