Re: GB18030-2022 Support in PostgreSQL

From: John Naylor <johncnaylorls(at)gmail(dot)com>
To: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>
Subject: Re: GB18030-2022 Support in PostgreSQL
Date: 2025-10-02 05:44:21
Message-ID: CANWCAZYGcjCxr5Ty5p_hCxQO_pjDC5hV9GCdxBn9Qx_FPUXf4w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 30, 2025 at 1:31 PM Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> wrote:
> Sure, no problem. Please see the attached v4, I reverted UHC change from v3. Again, please "git rm" the xml file when you push the commit.

Thanks, pushed after correcting the file name in the perl script
comment. I've marked the CF entry committed.

--
John Naylor
Amazon Web Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Joel Jacobson 2025-10-02 06:09:37 Teach pgbench to benchmark LISTEN/NOTIFY?
Previous Message Marina Polyakova 2025-10-02 05:39:02 Re: Use "?=" operator for a contrib makefile in documentation