| 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-18 08:53:08 |
| Message-ID: | CANWCAZZhsS4fu6Xyeo8L41Ga0Bkz31KNj2mMY82s7kVX8sJEiw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
John Naylor
Amazon Web Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2025-09-18 09:10:16 | Re: Marking shared buffer lookup table as HASH_FIXED_SIZE |
| Previous Message | Алена Васильева | 2025-09-18 08:44:57 | PATCH for BUG #18785: Pointer bmr.rel, dereferenced by passing as 1st parameter to function is checked for NULL later |