MIME-Version: 1.0
References: <176044409338.770.16064383081308443747@wrigleys.postgresql.org>
 <e9ad2cb03195402a96e8cb9130470bfca3bf49c7.camel@j-davis.com>
 <1307875.1760556576@sss.pgh.pa.us>
 <92151c4debb48bbbaed4db81c79d73c36f619858.camel@cybertec.at>
In-Reply-To: <92151c4debb48bbbaed4db81c79d73c36f619858.camel@cybertec.at>
From: Sergei Katkovsky <skatkovsky@gmail.com>
Date: Fri, 17 Oct 2025 18:18:08 +0400
Message-ID: 
 <CAAf8JyLJDtbBnx7zc_oPb=16YAHH0PyAh5H_GtZ7R0QJPqthNQ@mail.gmail.com>
Subject: Re: BPCHAR description in 8.3. Character Types is misleading and
 incomplete
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Jeff Davis <pgsql@j-davis.com>,
	pgsql-docs@lists.postgresql.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CAAf8JyLJDtbBnx7zc_oPb%3D16YAHH0PyAh5H_GtZ7R0QJPqthNQ%40mail.gmail.com>
Precedence: bulk

On Fri, Oct 17, 2025 at 4:49=E2=80=AFPM Laurenz Albe <laurenz.albe@cybertec=
.at> wrote:

> "bpchar" and "varchar", when used without type modifier, are actually
> identical:
>
> SELECT octet_length(BPCHAR 'x   '),
>        octet_length(VARCHAR 'x   '),
>        octet_length(TEXT 'x   ');
>
>  octet_length =E2=94=82 octet_length =E2=94=82 octet_length
> =E2=95=90=E2=95=90=E2=95=90=E2=95=90=E2=95=90=E2=95=90=E2=95=90=E2=95=90=
=E2=95=90=E2=95=90=E2=95=90=E2=95=90=E2=95=90=E2=95=90=E2=95=AA=E2=95=90=E2=
=95=90=E2=95=90=E2=95=90=E2=95=90=E2=95=90=E2=95=90=E2=95=90=E2=95=90=E2=95=
=90=E2=95=90=E2=95=90=E2=95=90=E2=95=90=E2=95=AA=E2=95=90=E2=95=90=E2=95=90=
=E2=95=90=E2=95=90=E2=95=90=E2=95=90=E2=95=90=E2=95=90=E2=95=90=E2=95=90=E2=
=95=90=E2=95=90=E2=95=90
>             4 =E2=94=82            4 =E2=94=82            4
>
> The blank-trimming only occurs when a "bpchar" is converted to "text",
> for example when used with the concatenation operator.

Unfortunately, BPCHAR and VARCHAR are not identical in other contexts.
The situation is not the same as with BCHAR(n), which is just an alias
for CHAR(n).
SELECT BPCHAR 'x' =3D VARCHAR 'x   ', VARCHAR 'x' =3D BPCHAR 'x   ',
VARCHAR 'x' =3D VARCHAR 'x   ';
true true false
For comparison with BPCHAR trailing blanks are insignificant, but when
we have VARCHAR on both sides, they matter.

With best regards,
Sergei Katkovskii