Re: GB18030-2022 Support in PostgreSQL - Mailing list pgsql-hackers

From Ken Marshall
Subject Re: GB18030-2022 Support in PostgreSQL
Date
Msg-id aJDl617Btp/2sDxf@customer.dllstxx1.pop.starlinkisp.net
Whole thread Raw
In response to GB18030-2022 Support in PostgreSQL  (JiaoShuntian <jiaoshuntian@highgo.com>)
List pgsql-hackers
On Mon, Aug 04, 2025 at 04:08:24PM +0800, JiaoShuntian wrote:
> Hi hackers,
> 
> I noticed that PostgreSQL currently supports GB18030 encoding based on the older GB18030-2000 standard (as seen in
commitslike 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
standardin 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
contributionsin this area?
 
> 
> Best regards,
> 
> JiaoShuntian
> HighGo Inc.

Hi,

I believe that it is in ICU already. You should be able to use that as
your locale provider.

Regards,
Ken



pgsql-hackers by date:

Previous
From: Sami Imseih
Date:
Subject: Re: Improve LWLock tranche name visibility across backends
Next
From: Melanie Plageman
Date:
Subject: Re: Missing import in 035_standby_logical_decoding.pl