Re: GB18030-2022 Support in PostgreSQL
| От | wenhui qiu |
|---|---|
| Тема | Re: GB18030-2022 Support in PostgreSQL |
| Дата | |
| Msg-id | CAGjGUAJnnqXcZyNxJ6ia9XGuS7FjRT6KTtYNjCx0EnPOv3ntxA@mail.gmail.com обсуждение исходный текст |
| Ответ на | GB18030-2022 Support in PostgreSQL (JiaoShuntian <jiaoshuntian@highgo.com>) |
| Список | pgsql-hackers |
Hi
😂，Not long ago, many people were rushing to remove this character set because of a security vulnerability. I was honestly quite shocked when I saw it.
Thanks
On Mon, Aug 4, 2025 at 4:08 PM JiaoShuntian <jiaoshuntian@highgo.com> wrote:
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.
В списке pgsql-hackers по дате отправления: