public inbox for [email protected]  

help / color / mirror / Atom feed

From: Bruce Momjian <[email protected]>
To: Alvaro Herrera <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: David G. Johnston <[email protected]>
Cc: [email protected]
Cc: Pg Docs <[email protected]>
Subject: Re: Documentation Suggestion
Date: Tue, 24 May 2022 08:36:18 -0400
Message-ID: <YozRQpzIo/[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <Yn6mY9ins/6c//[email protected]>
	<[email protected]>

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  <[email protected]>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Indecision is a decision.  Inaction is an action.  Mark Batterson

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Documentation Suggestion
  In-Reply-To: <YozRQpzIo/[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox