Date: Fri, 29 Apr 2022 11:09:14 +0200
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: jhebert@micron.com, Pg Docs <pgsql-docs@lists.postgresql.org>
Subject: Re: Documentation Suggestion
Message-ID: <202204290909.nuwx32e3jtjh@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="umxuhmay62rxegak"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CAKFQuwauo=ytCHOfV5udNhnoufPEN6uf9rpYsCauhjPWQry_Fg@mail.gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/202204290909.nuwx32e3jtjh%40alvherre.pgsql>
Precedence: bulk


--umxuhmay62rxegak
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit

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)

--umxuhmay62rxegak
Content-Type: text/x-diff; charset=utf-8
Content-Disposition: attachment;
	filename="0001-case-sensitivity-note-in-initdb.patch"