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

From Heikki Linnakangas
Subject Re: Retiring some encodings?
Date
Msg-id 2389d802-703e-41e4-953f-12d134523ef9@iki.fi
Whole thread Raw
List pgsql-hackers
On 22/05/2025 08:54, Michael Paquier wrote:
> With all that in mind, I have wanted to kick a discussion about
> potentially removing one or more encodings from the core code,
> including the backend part, the frontend part and the conversion
> routines, coupled with checks in pg_upgrade to complain with database
> or collations include the so-said encoding (the collation part needs
> to be checked when not using ICU).  Just being able to removing
> GB18030 would do us a favor in the long-term, at least, but there's
> more.

+1 at high level for deprecating and removing conversions that are not 
widely used anymore. As the first step, we can at least add a warning to 
the documentation, that they will be removed in the future.

-- 
Heikki Linnakangas
Neon (https://neon.tech)




pgsql-hackers by date:

Previous
From: Álvaro Herrera
Date:
Subject: Re: queryId constant squashing does not support prepared statements
Next
From: Pavel Stehule
Date:
Subject: Re: Retiring some encodings?