| From: | JiaoShuntian <jiaoshuntian(at)highgo(dot)com> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | GB18030-2022 Support in PostgreSQL |
| Date: | 2025-08-04 08:08:24 |
| Message-ID: | 966d9fc.169.198741fe60b.Coremail.jiaoshuntian@highgo.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi hackers,
I noticed that PostgreSQL currently supports GB18030 encoding based on the older GB18030-2000 standard (as seen in commits like extend GB18030 conversion). However, China has since updated its mandatory character set standard to GB18030-2022, which includes additional characters and stricter compliance requirements.GB18030-2022 is now the official standard in China, and ensuring PostgreSQL’s full compliance would be beneficial for users in Chinese-speaking regions.
I would like to ask:
Are there any plans to upgrade PostgreSQL’s GB18030 support to the 2022 version?Would the community be open to contributions in this area?
Best regards,
JiaoShuntian
HighGo Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shinya Kato | 2025-08-04 08:09:50 | Re: Add backup_type to pg_stat_progress_basebackup |
| Previous Message | Chao Li | 2025-08-04 07:57:49 | Re: Raw parse tree is not dumped to log |