public inbox for [email protected]  
help / color / mirror / Atom feed
From: Amit Kapila <[email protected]>
To: Peter Smith <[email protected]>
Cc: Álvaro Herrera <[email protected]>
Cc: Nisha Moond <[email protected]>
Cc: Jim Jones <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: PSQL - prevent describe listing tables that are already in listed schemas
Date: Mon, 15 Jun 2026 12:06:33 +0530
Message-ID: <CAA4eK1+e-a2nEA-fzQcE91vu8XpEC62R7tshPC14gp-jX1mqYg@mail.gmail.com> (raw)
In-Reply-To: <CAHut+PvaHNdgHoCfTq9K60PJpe_L7M3sswgiDe2R=XVEaOfapg@mail.gmail.com>
References: <CAHut+PtecJnFckGxEMT0-yhW=nTDR9aVcWpn_G+rFWTLTkP=YA@mail.gmail.com>
	<[email protected]>
	<CAHut+PvaHNdgHoCfTq9K60PJpe_L7M3sswgiDe2R=XVEaOfapg@mail.gmail.com>

On Mon, Jun 15, 2026 at 7:32 AM Peter Smith <[email protected]> wrote:
>
> On Fri, Jun 12, 2026 at 10:54 PM Álvaro Herrera <[email protected]> wrote:
> >
> > 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?
>
> FWIW, when I wrote this, in my mind I considered it more like the
> "quality of life improvement" because it is mostly about not
> displaying redundant information, rather than fixing any major bug.
>

+1. I also feel this should be considered as an improvement for PG20.

-- 
With Regards,
Amit Kapila.






view thread (20+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: PSQL - prevent describe listing tables that are already in listed schemas
  In-Reply-To: <CAA4eK1+e-a2nEA-fzQcE91vu8XpEC62R7tshPC14gp-jX1mqYg@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox