From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jeff Davis <pgsql@j-davis.com>
cc: skatkovsky@gmail.com, pgsql-docs@lists.postgresql.org
Subject: Re: BPCHAR description in 8.3. Character Types is misleading and
 incomplete
In-reply-to: <e9ad2cb03195402a96e8cb9130470bfca3bf49c7.camel@j-davis.com>
References: <176044409338.770.16064383081308443747@wrigleys.postgresql.org>
 <e9ad2cb03195402a96e8cb9130470bfca3bf49c7.camel@j-davis.com>
Comments: In-reply-to Jeff Davis <pgsql@j-davis.com>
	message dated "Wed, 15 Oct 2025 10:14:46 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1307874.1760556576.1@sss.pgh.pa.us>
Date: Wed, 15 Oct 2025 15:29:36 -0400
Message-ID: <1307875.1760556576@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1307875.1760556576%40sss.pgh.pa.us>
Precedence: bulk

Jeff Davis <pgsql@j-davis.com> writes:
> Please take a look at the attached patch. If you'd like your name
> included in the commit, please send it as you'd like it to appear.

I don't understand why any of these variants are better than the
original wording "blank-padded".  That has the non-negligible
advantage of corresponding to the type name, and furthermore
appears in many other places in our docs and source code.

There may be some other wording improvements we could make here,
but I think b69db5173 was fundamentally misguided in this respect.

			regards, tom lane