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 1nptkm-0004GF-NR for pgsql-docs@arkaria.postgresql.org; Sat, 14 May 2022 15:32:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nptkl-0006xV-Kc for pgsql-docs@arkaria.postgresql.org; Sat, 14 May 2022 15:32:23 +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 1npthk-00027a-Pa for pgsql-docs@lists.postgresql.org; Sat, 14 May 2022 15:29:16 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1npthg-0003dE-QO for pgsql-docs@lists.postgresql.org; Sat, 14 May 2022 15:29:16 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 0B4E05C0165; Sat, 14 May 2022 11:29:10 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Sat, 14 May 2022 11:29:10 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1652542150; x=1652628550; bh=57GAasH5riBvmA/25G3ZEaajlS6u zwEi/01aTzl40I0=; b=PUTduDrjPOmCeCJ5yT+dcsYTcQLM5cyy1zCRHKzzT2MX dtk3lvRVlrm9DFPmcqXDyRF+lo6JVf3lC3MLDEZiHn34bXMLf7LRZx+Xe2PtmgUf gext10SPtyACHgskP2ZLLP/B2HvYLir2c3k0ugucd8S1raX9JZeem6Dcco/K5V9v 0FnSzdVlNd8s5htOD0IoYIhiLB3ILZ4TWuf0BYzA+iGR8yUyW/Q/ybfkAbRMEIF+ Ocz0svGcPlD1zIISLIBpjMGhrUAEFI6o3jsVFvZyTKqLDL7eKS29ECbWmoVv0T/L syQJUlZQcPua32s9NpZcWlE6n5GG6KDHF7Z075Ouzw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrhedugdeklecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvvefukfggtggugfgjsehtkeertddttdejnecuhfhrohhmpeetlhhvrghr ohcujfgvrhhrvghrrgcuoegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhgqe enucggtffrrghtthgvrhhnpefgtdegleeggffftdeiuddufffhveekgfdufeethefgtefh kedvgeejlefhteehvdenucffohhmrghinhepvghnthgvrhhprhhishgvuggsrdgtohhmpd hpohhsthhgrhgvshhqlhdrohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgr mhepmhgrihhlfhhrohhmpegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhg X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat, 14 May 2022 11:29:09 -0400 (EDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 9E8F72A18AA; Sat, 14 May 2022 17:21:58 +0200 (CEST) Date: Sat, 14 May 2022 17:21:58 +0200 From: Alvaro Herrera To: Bruce Momjian Cc: Tom Lane , "David G. Johnston" , jhebert@micron.com, Pg Docs Subject: Re: Documentation Suggestion Message-ID: <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: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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. -- Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/ "I can see support will not be a problem. 10 out of 10." (Simon Wittber) (http://archives.postgresql.org/pgsql-general/2004-12/msg00159.php)