| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | DEVOPS_WwIT <devops(at)ww-it(dot)cn>, Michael Paquier <michael(at)paquier(dot)xyz>, Tatsuo Ishii <ishii(at)postgresql(dot)org>, wenhui qiu <qiuwenhuifx(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Bruce Momjian <bruce(at)momjian(dot)us>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, ZHU XIAN WEN <tony(dot)zhu(at)ww-it(dot)cn> |
| Subject: | Re: Retiring some encodings? |
| Date: | 2025-05-26 16:54:49 |
| Message-ID: | 7076C56C-70D1-440F-8559-50CF18E7D299@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 26 May 2025, at 18:07, Andrew Dunstan <andrew(at)dunslane(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2025-05-26 17:06:23 | Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly |
| Previous Message | Yugo Nagata | 2025-05-26 16:39:41 | Re: Prevent internal error at concurrent CREATE OR REPLACE FUNCTION |