| From: | Peter Smith <smithpb2250(at)gmail(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: DOCS - "\d mytable" also shows any publications that publish mytable |
| Date: | 2026-01-05 00:12:13 |
| Message-ID: | CAHut+Pvd=LMPsdoKQMh3z8PSG461wvd6odbT3RrrvMAi-+wWUw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Dec 25, 2025 at 11:45 AM Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
>
...
>
> \d table also seems to display tablespaces, policies, and other objects.
> Should the documentation try to list all possible objects that can be shown?
>
> If maintaining a complete list is difficult, would a more general description
> like "Associated objects, including indexes, constraints, rules, publications,
> and so on, are also shown." be sufficient instead of enumerating everything?
>
Hi Fujii-San.
Thanks for the review, and I agree with your point.
I prefer the suggestion for this description to be "correct" and
future-proof (albeit slightly generic). Listing too many details
doesn't add much value IMO and will be forever in need of
documentation maintenance.
PSA v3.
======
Kind Regards,
Peter Smith.
Fujitsu Australia
| Attachment | Content-Type | Size |
|---|---|---|
| v3-0001-DOCS-psql-describe-table-can-list-publications-an.patch | application/octet-stream | 2.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2026-01-05 00:21:59 | Re: index prefetching |
| Previous Message | Chao Li | 2026-01-04 23:42:52 | Re: intarray: fix an edge case int32 overflow bug |