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-09-29 04:03:09
Message-ID: CANWCAZZ9OyuVvthvhLzV0d9qumao2QSgKocSMT_DUzpnjuYUKA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Sep 24, 2025 at 4:18 PM Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> wrote:
> I am not sure if you should also upgrade the UCM file to 2022 version, but if we need, let’s do it with a separate commit.

If they can all use the same file, we should just do that for the sake
of simplicity, in which case a separate commit is just extra noise.

--
John Naylor
Amazon Web Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Chao Li 2025-09-29 04:18:21 Re: bug, ALTER TABLE call ATPostAlterTypeCleanup twice for the same relation
Previous Message shveta malik 2025-09-29 03:48:55 Re: Clear logical slot's 'synced' flag on promotion of standby