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

From: Nisha Moond <nisha(dot)moond412(at)gmail(dot)com>
To: Jim Jones <jim(dot)jones(at)uni-muenster(dot)de>
Cc: Peter Smith <smithpb2250(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: PSQL - prevent describe listing tables that are already in listed schemas
Date: 2026-05-20 08:27:58
Message-ID: CABdArM4_=HZjkQAxy5OA2u0h+ZLCacQGNQREot8-nXJ2QNTgbA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, May 20, 2026 at 1:00 PM Jim Jones <jim(dot)jones(at)uni-muenster(dot)de> wrote:
>
> Hi Nisha
>
> On 20/05/2026 09:09, Nisha Moond wrote:
> > For the describePublications (\dRp+) case, should we add an (sversion
> >> = 150000) guard around the new change, since it accesses
> > pg_publication_namespace, which is only available in PG15 and above?
> > Thoughts?
>
>
> I considered that in my first review, but since PG14 will be EOL'd by
> the time PG20 is shipped, I thought it wouldn't be necessary.
>

Okay, that makes sense.

--
Thanks,
Nisha

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jakub Wartak 2026-05-20 08:37:28 Re: pg_stat_io_histogram
Previous Message Antonin Houska 2026-05-20 07:54:06 Re: [PATCH] Fix REPACK decoding worker not cleaned up on FATAL exit