| From: | Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> |
|---|---|
| To: | John Naylor <johncnaylorls(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-18 08:16:05 |
| Message-ID: | 616C53FD-5C63-44C0-99CB-D51074A6DE22@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi John,
Thanks for working on v9.
> On Sep 18, 2025, at 15:59, John Naylor <johncnaylorls(at)gmail(dot)com> wrote:
>
>
> 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
> <v9-0001-Update-GB18030-encoding-from-version-2000-to-2022.patch>
V9 looks good to me. I am absolutely fine with removing the table of mapping changes.
When you say “communicate how to detect incompatibility for existing systems”, what would be the communication channel? I am actually very new to the PG development community, your guidance will be greatly appreciated.
Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2025-09-18 08:33:33 | Re: Proposal: Conflict log history table for Logical Replication |
| Previous Message | Daniel Gustafsson | 2025-09-18 08:14:40 | Re: someone else to do the list of acknowledgments |