Re: GB18030-2022 Support in PostgreSQL

Chao Li <li.evan.chao@gmail.com>

From: Chao Li <li.evan.chao@gmail.com>

To: John Naylor <johncnaylorls@gmail.com>

Cc: Peter Eisentraut <peter@eisentraut.org>, pgsql-hackers@lists.postgresql.org, Tom Lane <tgl@sss.pgh.pa.us>, Andrew Dunstan <andrew@dunslane.net>

Date: 2025-09-17T02:08:28Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Generate EUC_CN mappings from gb18030-2022.ucm
- 48566180efff 19 (unreleased) landed
Update GB18030 encoding from version 2000 to 2022
- 5334620eef8f 19 (unreleased) landed
Generate GB18030 mappings from the Unicode Consortium's UCM file
- cfa6cd29271e 19 (unreleased) landed

Attachments

v8-0001-Update-GB18030-encoding-from-version-2000-to-2022.patch (application/octet-stream) patch v8-0001

Hi John,

On Sep 16, 2025, at 17:36, John Naylor <johncnaylorls@gmail.com> wrote:


The comment change seems like it belongs in the preparatory commit
anyway, so I put the links there and pushed 0001 (along with the
squashed 0002).


Thank you very much for pushing 0001.

I see you have updated the function comment in utf8_and_gb18030.c, so I
removed it from the v8 patch.

Attached is the v8 patch:

* Updated the commit comment by taking your wording
* Removed the change of utf8_and_gb18030.c

Please take a look again, and thanks for your patience.

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/