| From: | John Naylor <johncnaylorls(at)gmail(dot)com> |
|---|---|
| To: | Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> |
| Cc: | 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-08-11 09:29:04 |
| Message-ID: | CANWCAZb4q8XUPL2S+S51Cbg8s_cBqasBPX_Ae6SDgbpkdk9Upw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Aug 11, 2025 at 4:25 PM Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> wrote:
>
> Sure I can split the patch into two. The patch only changes the .xml file to .ucm file and updating the perl script. As a result, map files should not be changed.
>
> Then the second patch will update the ucm file, so that the second patch should be small, contains only ucm changes and map file changes.
>
> One thing to confirm with you. To archive that, we will rename the ucm file as gb18030.ucm without suffix of “-2000” and “-2022”, otherwise git won’t be able to show the diff. Is that what you meant?
Usually git is pretty smart about renames combined with small changes,
so I would try keeping the original names and see what it does.
--
John Naylor
Amazon Web Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kirill Reshke | 2025-08-11 09:30:09 | Re: Parallel Apply |
| Previous Message | Chao Li | 2025-08-11 09:25:07 | Re: GB18030-2022 Support in PostgreSQL |