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

From John Naylor
Subject Re: GB18030-2022 Support in PostgreSQL
Date
Msg-id CANWCAZaaMtuMuWb+mT2GhCURHtnyPy_2doMOJK8t31wkA1u68w@mail.gmail.com
Whole thread Raw
In response to Re: GB18030-2022 Support in PostgreSQL  (Chao Li <li.evan.chao@gmail.com>)
Responses Re: GB18030-2022 Support in PostgreSQL
List pgsql-hackers
On Wed, Sep 17, 2025 at 9:08 AM Chao Li <li.evan.chao@gmail.com> wrote:
> 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:

I've reworked the commit message I started in v5 to incorporate later
discussions. (I was not a fan of including a complete table there, nor
of using UTF-8 encoding instead of code points as a reference.)

The only change I made for v9 is to reword the regression test
addition from "upgrades" to "change". I'm planning to commit next week
unless there are objections. (If anyone otherwise busy with the PG18
release wants a chance to weigh in, let me know and I'll hold off).

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

Attachment

pgsql-hackers by date:

Previous
From: Ashutosh Sharma
Date:
Subject: Re: How can end users know the cause of LR slot sync delays?
Next
From: Daniel Gustafsson
Date:
Subject: Re: someone else to do the list of acknowledgments