Re: Retiring some encodings?
| От | wenhui qiu |
|---|---|
| Тема | Re: Retiring some encodings? |
| Дата | |
| Msg-id | CAGjGUA+LNRTo34tqmnmhgJQ4k=tL8dY2DV80dj-ozh+rhXkE4Q@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Retiring some encodings? (Daniel Gustafsson <daniel@yesql.se>) |
| Список | 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?
> 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@yesql.se> wrote:
> On 23 May 2025, at 09:18, Heikki Linnakangas <hlinnaka@iki.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
В списке pgsql-hackers по дате отправления: