Re: Retiring some encodings?

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tatsuo Ishii <ishii(at)postgresql(dot)org>
Cc: daniel(at)yesql(dot)se, qiuwenhuifx(at)gmail(dot)com, hlinnaka(at)iki(dot)fi, bruce(at)momjian(dot)us, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Retiring some encodings?
Date: 2025-05-24 00:13:33
Message-ID: aDEPLWynq2fHscHc@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, May 23, 2025 at 07:58:46PM +0900, Tatsuo Ishii wrote:
> 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.

Yeah, that's a good point. I would also question what's the benefit
in using GB18030 over UTF-8, though. An obvious one I can see is
because legacy applications never get updated.

On my side, I'll try to grab some actual numbers or at least a trend
of them.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2025-05-24 00:17:14 Re: queryId constant squashing does not support prepared statements
Previous Message Michael Paquier 2025-05-24 00:10:50 Re: PG 18 release notes draft committed