| From: | Nisha Moond <nisha(dot)moond412(at)gmail(dot)com> |
|---|---|
| To: | Peter Smith <smithpb2250(at)gmail(dot)com> |
| Cc: | Jim Jones <jim(dot)jones(at)uni-muenster(dot)de>, 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 07:09:46 |
| Message-ID: | CABdArM6Ls0DRkqmpg5oDjwJhkrC9rvUQ9+y1jNmwRG+cq57cVQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 20, 2026 at 5:30 AM Peter Smith <smithpb2250(at)gmail(dot)com> wrote:
>
> I agree we should address that \d+ quirk at the same time.
>
> Thanks for finding/fixing it in v3-0002.
>
> Your 0002 patch works for me, although I'm thinking those SQL fixes
> ought to be made more similar:
> 1. Both use "n.oid NOT IN (SELECT pn.pnnspid ..."
> 2. Or both use "AND NOT EXISTS (SELECT 1 FROM ... WHERE ...)"
>
> ~
>
> PSA v4, where I have combined the patches, and chosen your SQL style
> for my previous \dRp+ fix.
>
+1 for the idea.
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?
--
Thanks,
Nisha
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jakub Wartak | 2026-05-20 07:16:28 | COPY TO BLACKHOLE / pg_dump -j -Fb |
| Previous Message | Fujii Masao | 2026-05-20 07:04:06 | Re: pg_recvlogical: honor source cluster file permissions for output files |