Content-Type: text/plain; charset="iso-8859-15"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: Built-in CTYPE provider
From: "Daniel Verite" <daniel@manitou-mail.org>
To: "Jeff Davis" <pgsql@j-davis.com>
Cc: Robert Haas <robertmhaas@gmail.com>,
 Jeremy Schneider <schneider@ardentperf.com>,
 pgsql-hackers@postgresql.org
In-Reply-To: <d9da5abdc0e485eef26937fe64e0af3b44098794.camel@j-davis.com>
Date: Fri, 12 Jan 2024 19:00:28 +0100
Message-Id: <1ecded1b-4ff8-46da-9b94-6e240db2a23b@manitou-mail.org>
Archived-At: 
 <https://www.postgresql.org/message-id/1ecded1b-4ff8-46da-9b94-6e240db2a23b%40manitou-mail.org>
Precedence: bulk

	Jeff Davis wrote:

> > Jeremy also raised a problem with old versions of psql connecting to
> > a
> > new server: the \l and \dO won't work. Not sure exactly what to do
> > there, but I could work around it by adding a new field rather than
> > renaming (though that's not ideal).
>=20
> I did a bit of research for a precedent, and the closest I could find
> is that \dp was broken between 14 and 15 by commit 07eee5a0dc.

Another one is that version 12 broke \d in older psql by
removing pg_class.relhasoids.

ISTM that in general the behavior of old psql vs new server does
not weight much against choosing optimal catalog changes.

There's also that warning at start informing users about it:
WARNING: psql major version X, server major version Y.
	 Some psql features might not work.


Best regards,
--=20
Daniel V=E9rit=E9
https://postgresql.verite.pro/
Twitter: @DanielVerite