Thread: Re: Retiring some encodings?

Hi,

On 2025-05-22 14:54:22 +0900, Michael Paquier wrote:
> All the encodings supported are documented here:
> https://www.postgresql.org/docs/devel/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED

There has been plenty discussion about GB18030, and it seems we aren't likely
to be able to drop that.

I think there are a lot easier cases though. The easiest probably is
MULE_INTERNAL - all discussions referencing it seem to be about oddities of
MULE_INTERNAL, not about using it.  I think it's been effectively unused since
it's introduction.  Due to not even having a conversion path to UTF-8 it's
really not practically usable IMO.

Greetings,

Andres Freund

On Thu, Jun 05, 2025 at 08:05:20PM -0400, Andres Freund wrote:
> There has been plenty discussion about GB18030, and it seems we aren't likely
> to be able to drop that.

Yes, as per upthread.

> I think there are a lot easier cases though. The easiest probably is
> MULE_INTERNAL - all discussions referencing it seem to be about oddities of
> MULE_INTERNAL, not about using it.  I think it's been effectively unused since
> it's introduction.  Due to not even having a conversion path to UTF-8 it's
> really not practically usable IMO.

Perhaps, yes.  I still need to do some homework here and gather some
data to share, FWIW.
--
Michael