| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Retiring some encodings? |
| Date: | 2025-05-22 12:05:03 |
| Message-ID: | CAFj8pRDbpcG+Pa6UVtZmOiuNBdROAD-TErTpbcBoutJGQn9Pzg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
čt 22. 5. 2025 v 13:44 odesílatel Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
napsal:
> 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.
>
+1
Pavel
> --
> Heikki Linnakangas
> Neon (https://neon.tech)
>
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Erik Nordström | 2025-05-22 12:13:39 | Relstats after VACUUM FULL and CLUSTER |
| Previous Message | Heikki Linnakangas | 2025-05-22 11:44:39 | Re: Retiring some encodings? |