From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | "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:09:14 |
Message-ID: | 202204290909.nuwx32e3jtjh@alvherre.pgsql |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On 2022-Apr-28, David G. Johnston wrote:
> But we don't go out of our way anywhere else to be so explicit about this
> kind of requirement and don't see a point of making this instance an
> exception.
Maybe we could add a <para> in the Options section before the item list,
along the lines of "be mindful that arguments to options --auth,
--auth-local, --encoding, --locale (and all --lc-* options) are
case-sensitive".
(The point here, I suppose, is that LDAP being an acronym is typically
spelled uppercase, so our use of lowercase is a bit odd.)
Maybe there are other places where this is relevant as well?
> The page could use a hyperlink/cross-reference to the pg_hba.conf
> documentation.
That's easily fixed. How about the attached patch?
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"El destino baraja y nosotros jugamos" (A. Schopenhauer)
Attachment | Content-Type | Size |
---|---|---|
0001-case-sensitivity-note-in-initdb.patch | text/x-diff | 2.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2022-04-29 09:52:45 | Re: Documentation Suggestion |
Previous Message | David G. Johnston | 2022-04-28 20:15:34 | Re: Documentation Suggestion |