Re: Character with byte sequence 0xa2 0xa3 in encoding "EUC_CN" has no equivalent in encoding "UTF8" - Mailing list pgsql-bugs

From Junwang Zhao
Subject Re: Character with byte sequence 0xa2 0xa3 in encoding "EUC_CN" has no equivalent in encoding "UTF8"
Date
Msg-id CAEG8a3+m6Hx-VzMBX92Y6EZECHhGDKS+2zHNkZC5FE0WkvWR3Q@mail.gmail.com
Whole thread
In response to Character with byte sequence 0xa2 0xa3 in encoding "EUC_CN" has no equivalent in encoding "UTF8"  (Zhongpu Chen <chenloveit@gmail.com>)
List pgsql-bugs
On Fri, May 1, 2026 at 9:59 PM Zhongpu Chen <chenloveit@gmail.com> wrote:
>
> ## Description
>
> The legacy encodings allow some invalid bytes, which will cause errors during SELECT operations.
>
> ## How to reproduce
>
> ```shell
> createdb -E EUC_CN -T template0 --locale=C demo_euc_cn_db
> ```
>
> ```sql
> demo_euc_cn_db=# CREATE TABLE t(id int, s varchar(10));
>
> demo_euc_cn_db=# INSERT INTO t VALUES(1, E'\xA2\xA3');
> INSERT 0 1
> demo_euc_cn_db=# SELECT * FROM t WHERE id = 1;
> ERROR:  character with byte sequence 0xa2 0xa3 in encoding "EUC_CN" has no equivalent in encoding "UTF8"

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

> ```
>
> --
> Zhongpu Chen



--
Regards
Junwang Zhao



pgsql-bugs by date:

Previous
From: Zhongpu Chen
Date:
Subject: Character with byte sequence 0xa2 0xa3 in encoding "EUC_CN" has no equivalent in encoding "UTF8"
Next
From: Zhongpu Chen
Date:
Subject: Re: Character with byte sequence 0xa2 0xa3 in encoding "EUC_CN" has no equivalent in encoding "UTF8"