Re: Retiring some encodings? - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: Retiring some encodings?
Date
Msg-id 20602C66-8364-4043-A089-1C257F917E7E@yesql.se
Whole thread Raw
In response to Re: Retiring some encodings?  (wenhui qiu <qiuwenhuifx@gmail.com>)
List pgsql-hackers
> On 23 May 2025, at 11:08, wenhui qiu <qiuwenhuifx@gmail.com> wrote:
>
> HI
> > The obvious question is how many people would suffer because
> > of that removal, as it would prevent them from using pg_upgrade.
>
> > Can anybody who works in a region that uses these encodings make
> > an educated guess?
> +1 Agree ,GB18030 A coding standard in China, if deleted, will have an impact on the application of postgresql in
China,and China is now experiencing more and more hot postgresql heat, need to consider carefully! 

Thanks for the input, that's exactly what we need to make informed decisions.
How prevalent is GB18030 usage, is it used in all postgres installations in
China, most of them or in some particular cases?

--
Daniel Gustafsson




pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: Enable data checksums by default
Next
From: Tomas Vondra
Date:
Subject: Re: Enable data checksums by default