From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | jhebert(at)micron(dot)com, Pg Docs <pgsql-docs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Documentation Suggestion |
Date: | 2022-04-29 09:52:45 |
Message-ID: | 4f128d4d-66b3-a5ec-2e8e-c67511dd39a3@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On 29.04.22 11:09, Alvaro Herrera wrote:
> + <para>
> + Be mindful that arguments to options <option>--auth</option>,
> + <option>--auth-local</option>, <option>--encoding</option>,
> + <option>--locale</option> (and all <option>--lc-*</option> options) are
> + case-sensitive.
> + </para>
Almost all arguments of command-line options of all PostgreSQL tools are
case-sensitive. Consider the initdb -U option for example. By pointing
out a couple of specific cases, wouldn't we also create more confusion
about options not mentioned?
(I'm not sure about the case-sensitivity of the locale options. That
could be OS-dependent.)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-04-29 14:06:57 | Re: Documentation Suggestion |
Previous Message | Alvaro Herrera | 2022-04-29 09:09:14 | Re: Documentation Suggestion |