Re: Character with byte sequence 0xa2 0xa3 in encoding "EUC_CN" has no equivalent in encoding "UTF8"

From: Junwang Zhao <zhjwpku(at)gmail(dot)com>
To: Zhongpu Chen <chenloveit(at)gmail(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Character with byte sequence 0xa2 0xa3 in encoding "EUC_CN" has no equivalent in encoding "UTF8"
Date: 2026-05-01 15:07:16
Message-ID: CAEG8a3+m6Hx-VzMBX92Y6EZECHhGDKS+2zHNkZC5FE0WkvWR3Q@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, May 1, 2026 at 9:59 PM Zhongpu Chen <chenloveit(at)gmail(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Zhongpu Chen 2026-05-01 16:09:19 Re: Character with byte sequence 0xa2 0xa3 in encoding "EUC_CN" has no equivalent in encoding "UTF8"
Previous Message Zhongpu Chen 2026-05-01 13:59:18 Character with byte sequence 0xa2 0xa3 in encoding "EUC_CN" has no equivalent in encoding "UTF8"