Horton

Re: GB18030-2022 Support in PostgreSQL

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

View thread
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-18T08:16:05Z
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 →

  1. Generate EUC_CN mappings from gb18030-2022.ucm

  2. Update GB18030 encoding from version 2000 to 2022

  3. Generate GB18030 mappings from the Unicode Consortium's UCM file

Hi John,

Thanks for working on v9.

> On Sep 18, 2025, at 15:59, John Naylor <johncnaylorls@gmail.com> wrote:
> 
> 
> It'll be a good idea to communicate how to detect (unlikely but not
> impossible) incompatibilities for existing systems, but I don't think
> committing needs to wait for that piece.
> 
> --
> John Naylor
> Amazon Web Services
> <v9-0001-Update-GB18030-encoding-from-version-2000-to-2022.patch>


V9 looks good to me. I am absolutely fine with removing the table of mapping changes.

When you say “communicate how to detect incompatibility for existing systems”, what would be the communication channel? I am actually very new to the PG development community, your guidance will be greatly appreciated.

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