Horton

Re: Retiring some encodings?

Tatsuo Ishii <ishii@postgresql.org>

View thread
From: Tatsuo Ishii <ishii@postgresql.org>
To: myon@debian.org
Cc: michael@paquier.xyz, daniel@yesql.se, andrew@dunslane.net, devops@ww-it.cn, ishii@postgresql.org, qiuwenhuifx@gmail.com, hlinnaka@iki.fi, bruce@momjian.us, pgsql-hackers@lists.postgresql.org, tony.zhu@ww-it.cn
Date: 2025-06-05T23:50:56Z
Lists: pgsql-hackers 
>> Agreed that the so-said "state" level requirement would be a
>> non-starter.
> 
> Or maybe support for using these as server encodings could be
> removed, keeping the client_encoding part intact?

GB18030 is already client encoding only, and cannot be used as a
server encoding. The only way to save GB18030 data into database is,
converting GB18030 to UTF-8 (which can be done automatically).

Best regards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp