| From: | wenhui qiu <qiuwenhuifx(at)gmail(dot)com> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Michael Paquier <michael(at)paquier(dot)xyz>, Bruce Momjian <bruce(at)momjian(dot)us>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Retiring some encodings? |
| Date: | 2025-05-23 09:08:35 |
| Message-ID: | CAGjGUA+LNRTo34tqmnmhgJQ4k=tL8dY2DV80dj-ozh+rhXkE4Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
HI
> The obvious question is how many people would suffer because
> of that removal, as it would prevent them from using pg_upgrade.
> Can anybody who works in a region that uses these encodings make
> an educated guess?
+1 Agree ,GB18030 A coding standard in China, if deleted, will have an
impact on the application of postgresql in China, and China is now
experiencing more and more hot postgresql heat, need to consider carefully!
On Fri, May 23, 2025 at 4:22 PM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> > On 23 May 2025, at 09:18, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
>
> > If we plan to remove something in the future, I think putting a
> deprecation notice in the docs in v18 is still a good idea. There's no
> point in hiding the plan by not documenting it sooner. The more advance
> notice people get the better.
>
> +1
>
> --
> Daniel Gustafsson
>
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2025-05-23 09:22:29 | Re: Enable data checksums by default |
| Previous Message | Amit Kapila | 2025-05-23 08:56:59 | Re: Conflict detection for update_deleted in logical replication |