Re: Retiring some encodings?

From: Christoph Berg <myon(at)debian(dot)org>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Daniel Gustafsson <daniel(at)yesql(dot)se>, Andrew Dunstan <andrew(at)dunslane(dot)net>, DEVOPS_WwIT <devops(at)ww-it(dot)cn>, Tatsuo Ishii <ishii(at)postgresql(dot)org>, wenhui qiu <qiuwenhuifx(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Bruce Momjian <bruce(at)momjian(dot)us>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, ZHU XIAN WEN <tony(dot)zhu(at)ww-it(dot)cn>
Subject: Re: Retiring some encodings?
Date: 2025-06-05 13:35:19
Message-ID: aEGdF2lKRI_95D73@msg.df7cb.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Re: Michael Paquier
> On Mon, May 26, 2025 at 06:54:49PM +0200, Daniel Gustafsson wrote:
> > Agreed, it seems very unappealing to remove something so important to such a
> > large userbase.
>
> Agreed that the so-said "state" level requirement would be a
> non-starter.

Or maybe support for using these as server encodings could be
removed, keeping the client_encoding part intact?

Christoph

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ayush Vatsa 2025-06-05 13:47:28 Re: Question Regarding Merge Append and Parallel Execution of Index Scans on Partitioned Table
Previous Message Ashutosh Bapat 2025-06-05 13:24:04 Re: pg_get_multixact_members not documented