Feedback-ID: ie3de48e3:Fastmail
Date: Fri, 12 Jun 2026 14:53:55 +0200
From: =?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@kurilemu.de>
To: Peter Smith <smithpb2250@gmail.com>
Cc: Nisha Moond <nisha.moond412@gmail.com>,
	Jim Jones <jim.jones@uni-muenster.de>,
 PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: PSQL - prevent describe listing tables that are already in
 listed schemas
Message-ID: <aiv9oBhW8mL_F8Yn@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CAHut+PtecJnFckGxEMT0-yhW=nTDR9aVcWpn_G+rFWTLTkP=YA@mail.gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/aiv9oBhW8mL_F8Yn%40alvherre.pgsql>
Precedence: bulk

On 2026-May-21, Peter Smith wrote:

> The new tests in patch v5 look good to me.

So do we want to consider this a backpatchable bugfix, or just a
new-feature-ish quality of life improvement?  If the former, then we
should probably backpatch it; otherwise we would normally wait until
pg20 opens.  Though to be honest I would also consider this as
borderline okay to include in pg19 for beta2 -- especially considering
that the output in 19 is already changed by the EXCEPT TABLE listing
additions.

Given that it applies to servers back to 15, that means that in the
situation where it applies, pg19's psql (or pg20's) output would be
different than earlier ones given identical database state.  I'm not
sure that would be really great.

What do others think?

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/