Horton

Re: Retiring some encodings?

Daniel Gustafsson <daniel@yesql.se>

View thread
From: Daniel Gustafsson <daniel@yesql.se>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: DEVOPS_WwIT <devops@ww-it.cn>, Michael Paquier <michael@paquier.xyz>, Tatsuo Ishii <ishii@postgresql.org>, wenhui qiu <qiuwenhuifx@gmail.com>, Heikki Linnakangas <hlinnaka@iki.fi>, Bruce Momjian <bruce@momjian.us>, Postgres hackers <pgsql-hackers@lists.postgresql.org>, ZHU XIAN WEN <tony.zhu@ww-it.cn>
Date: 2025-05-26T16:54:49Z
Lists: pgsql-hackers 
> On 26 May 2025, at 18:07, Andrew Dunstan <andrew@dunslane.net> wrote:
> On 2025-05-24 Sa 8:58 PM, DEVOPS_WwIT wrote:

>> The GB18030 encoding standard is a mandatory Chinese character encoding standard required by regulations. Software sold and used in China must support GB18030, with its latest version being the 2023 edition. The primary advantage of GB18030 is that most Chinese characters require only 2 bytes for storage, whereas UTF-8 necessitates 3 bytes for the same characters. This makes GB18030 significantly more storage-efficient compared to UTF-8 in terms of space utilization.
> 
> Given this, removing it seems like a non-starter.

Agreed, it seems very unappealing to remove something so important to such a
large userbase.

--
Daniel Gustafsson