| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | daniel(at)yesql(dot)se |
| Cc: | qiuwenhuifx(at)gmail(dot)com, hlinnaka(at)iki(dot)fi, michael(at)paquier(dot)xyz, bruce(at)momjian(dot)us, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Retiring some encodings? |
| Date: | 2025-05-23 10:58:46 |
| Message-ID: | 20250523.195846.842630502869511194.ishii@postgresql.org |
| Views: | Raw Message | Whole Thread | 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?
Another point is, whether other DBMS support GB18030 or not. If they
support, but PostgreSQL would not in the future, that could be a
reason to move away from PostgreSQL.
As far as I know MySQL, Oracle and SQL server support GB18030.
Best regards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2025-05-23 11:07:37 | Re: Conflict detection for update_deleted in logical replication |
| Previous Message | Jim Jones | 2025-05-23 10:15:10 | Re: [PoC] XMLCast (SQL/XML X025) |