Re: A suggestion about the usage manual of \d command

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: yuanchao zhang <zhangyc0706(at)gmail(dot)com>
Cc: "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org>
Subject: Re: A suggestion about the usage manual of \d command
Date: 2026-02-28 01:09:30
Message-ID: CAKFQuwYF1=U-1MVagLgXOVzGer1qXagCpo1_i621uyRsqRzjuw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Fri, Feb 27, 2026 at 6:02 PM yuanchao zhang <zhangyc0706(at)gmail(dot)com>
wrote:

> Okay, no problem. I just encountered this issue and was experiencing some
> inconvenience as a user. If I have more detailed thoughts, I can add them
> later. Thank you for your reply anyway.
>

Fair, and I do appreciate the confusion experienced. But I also think that
the whole flow of "I named my domain numeric and didn't see it in \dD" is
more of a feature than a bug. It ultimately made you aware of the shadowing
with the other base type named numeric and the idea that maybe naming a
domain that isn't a good idea - or that in doing so you at least need to
learn the consequences.

That, and given few complaints of this nature, and the fact we cannot at
this point change the policy that \d commands limit output based on
visibility, means the easy fixes to deal with this specific complaint are
unavailable even if they seem worthwhile (of which I have my doubts).

David J.

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message PG Doc comments form 2026-02-28 08:36:30 Documentation incorrect pg_partition_root function description.
Previous Message yuanchao zhang 2026-02-28 01:02:47 Re: A suggestion about the usage manual of \d command