Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ntTqq-0007VI-6B for pgsql-docs@arkaria.postgresql.org; Tue, 24 May 2022 12:41:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ntTqp-0003Vy-0j for pgsql-docs@arkaria.postgresql.org; Tue, 24 May 2022 12:41:27 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ntTqo-0003VW-PL for pgsql-docs@lists.postgresql.org; Tue, 24 May 2022 12:41:26 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ntTqm-0008HY-Fk for pgsql-docs@lists.postgresql.org; Tue, 24 May 2022 12:41:26 +0000 Received: from bruce by momjian.us with local (Exim 4.94.2) (envelope-from ) id 1ntTlq-006qBX-2k; Tue, 24 May 2022 08:36:18 -0400 Date: Tue, 24 May 2022 08:36:18 -0400 From: Bruce Momjian To: Alvaro Herrera Cc: Tom Lane , "David G. Johnston" , jhebert@micron.com, Pg Docs Subject: Re: Documentation Suggestion Message-ID: References: <202205141521.2nodjabmsour@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <202205141521.2nodjabmsour@alvherre.pgsql> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk fOn Sat, May 14, 2022 at 05:21:58PM +0200, Álvaro Herrera wrote: > I pushed the other suggested bits. > > On 2022-May-13, Bruce Momjian wrote: > > > On Fri, Apr 29, 2022 at 10:06:57AM -0400, Tom Lane wrote: > > > > I don't think this is an improvement, mainly for the reason David > > > mentions: why wouldn't you need a similar statement on every single > > > one of our program man pages? > > > > I think the confusion is that while the option arguments are > > case-sensitive, many of the values are typically used as all upper-case, > > and I think any doc mention would have to include that: > > > > Note that valid --auth option values are all lower case, even > > for authentication types that typically appear as all upper case, > > e.g., "LDAP". > > Yeah, that was my initial thought too. The case-sensitivity is a > consideration for other things too (such as locale or encoding names), > but for those we do match the operating system name exactly, rather than > using our own lower-case version of it, which nobody else uses. > > So really the point is not about the fact that it is case sensitive as > that the case of our name doesn't match the usual one. Maybe the note > should be "Note that authentication types are all lower case, [even for > ...]" or something like that. Agreed. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Indecision is a decision. Inaction is an action. Mark Batterson