| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Retiring some encodings? |
| Date: | 2025-06-06 00:05:20 |
| Message-ID: | o2mxoan74gy4xjbfmyy47u3elqt4xdjqji4yvfabldnnl2mbfg@yji5fo6uaig2 |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sami Imseih | 2025-06-06 00:16:14 | Re: [PATCH] Re: Proposal to Enable/Disable Index using ALTER INDEX |
| Previous Message | Tom Lane | 2025-06-06 00:01:30 | Re: We should lazy-initialize the deadlock checker state memory |