MIME-Version: 1.0
References: <CA+1gyqL7uiQhfLcYWpHNUKQgHjQc7sOPthSTiaxLDZzcrGFYSg@mail.gmail.com>
In-Reply-To: <CA+1gyqL7uiQhfLcYWpHNUKQgHjQc7sOPthSTiaxLDZzcrGFYSg@mail.gmail.com>
From: Junwang Zhao <zhjwpku@gmail.com>
Date: Fri, 1 May 2026 23:07:16 +0800
Message-ID: <CAEG8a3+m6Hx-VzMBX92Y6EZECHhGDKS+2zHNkZC5FE0WkvWR3Q@mail.gmail.com>
Subject: Re: Character with byte sequence 0xa2 0xa3 in encoding "EUC_CN" has
 no equivalent in encoding "UTF8"
To: Zhongpu Chen <chenloveit@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CAEG8a3%2Bm6Hx-VzMBX92Y6EZECHhGDKS%2B2zHNkZC5FE0WkvWR3Q%40mail.gmail.com>
Precedence: bulk

On Fri, May 1, 2026 at 9:59=E2=80=AFPM Zhongpu Chen <chenloveit@gmail.com> =
wrote:
>
> ## Description
>
> The legacy encodings allow some invalid bytes, which will cause errors du=
ring SELECT operations.
>
> ## How to reproduce
>
> ```shell
> createdb -E EUC_CN -T template0 --locale=3DC demo_euc_cn_db
> ```
>
> ```sql
> demo_euc_cn_db=3D# CREATE TABLE t(id int, s varchar(10));
>
> demo_euc_cn_db=3D# INSERT INTO t VALUES(1, E'\xA2\xA3');
> INSERT 0 1
> demo_euc_cn_db=3D# SELECT * FROM t WHERE id =3D 1;
> ERROR:  character with byte sequence 0xa2 0xa3 in encoding "EUC_CN" has n=
o equivalent in encoding "UTF8"

Can you try the following statement before select?
SET client_encoding TO 'EUC_CN';

> ```
>
> --
> Zhongpu Chen


--=20
Regards
Junwang Zhao