Re: GB18030-2022 Support in PostgreSQL

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(at)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/