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-08-18T08:50:34Z
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

Attachments

On 2025/8/18 16:34, John Naylor wrote:
> I verified that both autoconf and meson builds pick up the change with
> these two patches, and the new test passes. I'm still not sure what
> circumstances you found where a change doesn't get picked up, but we
> can come back to that later if need be.

Let's talk about the makefile change separately.

> ...and confusingly v2 needed to be applied first. To create a series
> from a branch, use `git format-patch master -v <version number>` and
> it will output an ordered series with one patch per commit.


This is my first spitted patch. I was confused about the "0001" part in 
patch file names. Now I understood. I just recreated the both patch 
files as v3:

chaol@ChaodeMacBook-Air postgresql % git format-patch -v3 master 
v3-0001-GB18030-Switch-to-using-gb-18030-2000.ucm.patch 
v3-0002-Upgrade-GB18030-encoding-support-from-2000-to-202.patch

Regard regards,

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