| 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 09:44:43 |
| Message-ID: | 3577EF3F-03FC-4928-A677-EF7AE28C8BF1@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Sep 18, 2025, at 16:53, John Naylor <johncnaylorls(at)gmail(dot)com> wrote:
>
> On Thu, Sep 18, 2025 at 3:16 PM Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> wrote:
>>
>> 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.
>
> My first thought was to include a sample query in the release notes
> that filters on text with the affected code points, but I'd be happy
> to hear other ideas. We start working on release notes around
> April/May.
>
So, no immediate action to take, right? I may work out such a query before starting of release note work.
Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Frédéric Yhuel | 2025-09-18 09:52:12 | Re: [BUG] temporary file usage report with extended protocol and unnamed portals |
| Previous Message | Daniel Gustafsson | 2025-09-18 09:25:38 | Re: someone else to do the list of acknowledgments |