Re: PSQL - prevent describe listing tables that are already in listed schemas

On Fri, Jun 12, 2026 at 10:54 PM Álvaro Herrera <alvherre(at)kurilemu(dot)de> 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.

AFAICT this is quite an old problem that nobody ever found/reported it
before, so even though I had intended this for PG19 (and posted before
the freeze), it is fine by me if you prefer to leave it until PG20
because I don't think anybody will miss it.

======
Kind Regards,
Peter Smith.
Fujitsu Australia