MIME-Version: 1.0
References: <CA+1gyqL7uiQhfLcYWpHNUKQgHjQc7sOPthSTiaxLDZzcrGFYSg@mail.gmail.com>
 <CAEG8a3+m6Hx-VzMBX92Y6EZECHhGDKS+2zHNkZC5FE0WkvWR3Q@mail.gmail.com> <CA+1gyqJMtuTofZDy+CeomGGhsFGXw6JrdyAhqvnLii44oKePGg@mail.gmail.com>
In-Reply-To: <CA+1gyqJMtuTofZDy+CeomGGhsFGXw6JrdyAhqvnLii44oKePGg@mail.gmail.com>
From: Junwang Zhao <zhjwpku@gmail.com>
Date: Sat, 2 May 2026 09:25:20 +0800
Message-ID: <CAEG8a3+ithNTBCsuu88tecUDx+VjABkCoOjuKyxgMX29hSTX-g@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%2BithNTBCsuu88tecUDx%2BVjABkCoOjuKyxgMX29hSTX-g%40mail.gmail.com>
Precedence: bulk

On Sat, May 2, 2026 at 12:09=E2=80=AFAM Zhongpu Chen <chenloveit@gmail.com>=
 wrote:
>
>
> ```
> demo_euc_cn_db=3D# SET client_encoding TO 'EUC_CN';
> SET
> demo_euc_cn_db=3D# SELECT * FROM t WHERE id =3D 1;
>  id | s
> ----+----
>   1 | =EF=BF=BD=EF=BF=BD
> (1 row)
> ```
>
> Since 0xA2A3 is invalid in EUC-CN, it cannot be mapped to any meaningful =
character. Currently, EUC-CN allows all 2-byte within A1-EF, but this coars=
e-grained approach is flawed.

This seems more like a feature request than a bug. It would make sense
to close the bug report and start a discussion on the hackers mailing
list instead.

>
> On Fri, May 1, 2026 at 11:07=E2=80=AFPM Junwang Zhao <zhjwpku@gmail.com> =
wrote:
>>
>> On Fri, May 1, 2026 at 9:59=E2=80=AFPM Zhongpu Chen <chenloveit@gmail.co=
m> 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=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" ha=
s no equivalent in encoding "UTF8"
>>
>> Can you try the following statement before select?
>> SET client_encoding TO 'EUC_CN';
>>
>> > ```
>> >
>> > --
>> > Zhongpu Chen
>>
>>
>>
>> --
>> Regards
>> Junwang Zhao
>
>
>
> --
> Zhongpu Chen


--=20
Regards
Junwang Zhao