Message-ID: <41fe0ea52f9803649ae876d4d14b2b7ca89ffc06.camel@cybertec.at>
Subject: Re: suggest about bpchar  data type in the document
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: yanliang lei <msdnchina@163.com>, "pgsql-docs@lists.postgresql.org"
	 <pgsql-docs@lists.postgresql.org>
Date: Wed, 14 Sep 2022 18:48:46 +0200
In-Reply-To: <120b3084.56b6.1833b5ffe4b.Coremail.msdnchina@163.com>
References: <120b3084.56b6.1833b5ffe4b.Coremail.msdnchina@163.com>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.42.4 (3.42.4-2.fc35) 
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/41fe0ea52f9803649ae876d4d14b2b7ca89ffc06.camel%40cybertec.at>
Precedence: bulk

On Wed, 2022-09-14 at 17:41 +0800, yanliang lei wrote:
> I hope that：
> 
>  in the  https://www.postgresql.org/docs/14/datatype-characterin.html ，It needs to be written clearly  “bpchar” data type，
> 
> and in the above url, Only mentioned “blank padded” ，If someone does not know  this knowledge point（blank padded =bp），he/she  will make a detour in the study of  character datatype。
> 
> so，To make the document more friendly, I suggest that： in the  https://www.postgresql.org/docs/14/datatype-characterin.htm  ，It needs to be written clearly  “bpchar” data type。

+1

I think that adding "bpchar(n)" in table 8.4 would be a good thing.

Yours,
Laurenz Albe