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.
