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-30 06:05:42
Message-ID: CANWCAZb7_adtR7FLtCHU5yev0A5bQZRUFeRfbVepY1tO2xC4VQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Sep 29, 2025 at 5:36 PM Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> wrote:
> “same file" was a mistake. windows-949-2000.ucm is a different file from gb-18030-2000(2022).ucm.
>
> In theory, we don’t need to change UHC if our goal is to delete gb-18030-2000.xml.

That was my goal, yes. Let's stay focused on that and not change
unrelated things.

--
John Naylor
Amazon Web Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Yugo Nagata 2025-09-30 06:16:53 Re: Suggestion to add --continue-client-on-abort option to pgbench
Previous Message shveta malik 2025-09-30 05:57:59 Re: POC: enable logical decoding when wal_level = 'replica' without a server restart