| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | wenhui qiu <qiuwenhuifx(at)gmail(dot)com> |
| Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Michael Paquier <michael(at)paquier(dot)xyz>, Bruce Momjian <bruce(at)momjian(dot)us>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Retiring some encodings? |
| Date: | 2025-05-23 09:28:32 |
| Message-ID: | 20602C66-8364-4043-A089-1C257F917E7E@yesql.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 23 May 2025, at 11:08, wenhui qiu <qiuwenhuifx(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2025-05-23 09:43:57 | Re: Enable data checksums by default |
| Previous Message | Daniel Gustafsson | 2025-05-23 09:25:56 | Re: Enable data checksums by default |