| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, John Naylor <johncnaylorls(at)gmail(dot)com>, JiaoShuntian <jiaoshuntian(at)highgo(dot)com(dot)w(dot)kunlunaq(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: GB18030-2022 Support in PostgreSQL |
| Date: | 2025-08-06 10:29:15 |
| Message-ID: | 67669282-145d-437b-ba29-805216c13597@eisentraut.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 05.08.25 08:22, Chao Li wrote:
> I agree with Tom that we may just redefine GB18030 to comply with the
> 2022 standard.
>
> As John Naylor pointed, 2022 is not backward compatible, that is true.
> However, I went through all the incompatible changes, those are all
> characters rarely used. So I would guess most of the existing databases
> won’t be impacted and the rest with encoding GB18030 need to do data
> migration before upgrading to a PG version that switches to
> GB18030-2022. I think PG may delegate data migration tasks to third
> party PG service vendors. They may develop simple or complex migration
> tools to help different use cases.
Note that you can also create custom conversions using CREATE
CONVERSION, so that would be something for those who would need the old
behavior.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Álvaro Herrera | 2025-08-06 10:44:13 | Re: LISTEN/NOTIFY bug: VACUUM sets frozenxid past a xid in async queue |
| Previous Message | Álvaro Herrera | 2025-08-06 09:41:46 | Re: Enhance Makefiles to rebuild objects on map file changes |