From: Tom Lane <tgl@sss.pgh.pa.us>
To: Christoph Berg <myon@debian.org>
cc: pgsql-hackers@lists.postgresql.org
Subject: Re: pgsql: Improve default and empty privilege outputs in psql.
In-reply-to: <ZvLXYglRS6hMMhtr@msg.df7cb.de>
References: <E1r2dkc-005J8F-Qc@gemulon.postgresql.org> <ZvLXYglRS6hMMhtr@msg.df7cb.de>
Comments: In-reply-to Christoph Berg <myon@debian.org>
	message dated "Tue, 24 Sep 2024 17:14:42 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3361176.1727195279.1@sss.pgh.pa.us>
Date: Tue, 24 Sep 2024 12:27:59 -0400
Message-ID: <3361177.1727195279@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/3361177.1727195279%40sss.pgh.pa.us>
Precedence: bulk

Christoph Berg <myon@debian.org> writes:
> Re: Tom Lane
>> Improve default and empty privilege outputs in psql.

> I'm sorry to report this when 17.0 has already been wrapped, but this
> change is breaking `psql -l` against 9.3-or-earlier servers:
> FEHLER:  42883: Funktion pg_catalog.cardinality(aclitem[]) existiert nicht

Grumble.  Well, if that's the worst bug in 17.0 we should all be
very pleased indeed ;-).  I'll see about fixing it after the
release freeze lifts.

> The psql docs aren't really explicit about which old versions are
> still supported, but there's some mentioning that \d should work back
> to 9.2:

Yes, that's the expectation.  I'm sure we can think of a more
backwards-compatible way to test for empty datacl, though.

			regards, tom lane