MIME-Version: 1.0
References: 
 <CAADcJZO6M3aOfkY344wQUjRiOJCgPtfiMBCtqyuFzp6o8_5nxw@mail.gmail.com>
 <CAKFQuwbM3Vk9MeSa5e6G6APY5A8vmtOL_sh=7fYy6YqOpsooJg@mail.gmail.com>
 <CAADcJZOaae_jsiEQuW=58hwwPjZB47Jv9Mhf8H4KAJ_GANwa5Q@mail.gmail.com>
In-Reply-To: 
 <CAADcJZOaae_jsiEQuW=58hwwPjZB47Jv9Mhf8H4KAJ_GANwa5Q@mail.gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
Date: Fri, 27 Feb 2026 18:09:30 -0700
Message-ID: 
 <CAKFQuwYF1=U-1MVagLgXOVzGer1qXagCpo1_i621uyRsqRzjuw@mail.gmail.com>
Subject: Re: A suggestion about the usage manual of \d command
To: yuanchao zhang <zhangyc0706@gmail.com>
Cc: "pgsql-docs@lists.postgresql.org" <pgsql-docs@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000009f35ca064bd803a0"
Archived-At: 
 <https://www.postgresql.org/message-id/CAKFQuwYF1%3DU-1MVagLgXOVzGer1qXagCpo1_i621uyRsqRzjuw%40mail.gmail.com>
Precedence: bulk

--0000000000009f35ca064bd803a0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Feb 27, 2026 at 6:02=E2=80=AFPM yuanchao zhang <zhangyc0706@gmail.c=
om>
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.

--0000000000009f35ca064bd803a0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon=
t-family:arial,helvetica,sans-serif"><span style=3D"font-family:Arial,Helve=
tica,sans-serif">On Fri, Feb 27, 2026 at 6:02=E2=80=AFPM yuanchao zhang &lt=
;<a href=3D"mailto:zhangyc0706@gmail.com">zhangyc0706@gmail.com</a>&gt; wro=
te:</span></div></div><div class=3D"gmail_quote gmail_quote_container"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Okay, no pro=
blem. 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 y=
ou for your reply anyway.</div></blockquote><div><br></div><div class=3D"gm=
ail_default" style=3D"font-family:arial,helvetica,sans-serif">Fair, and I d=
o appreciate the confusion experienced.=C2=A0 But I also think that the who=
le flow of &quot;I named my domain numeric and didn&#39;t see it in \dD&quo=
t; is more of a feature than a bug. It ultimately made you aware of the sha=
dowing with the other base type named numeric and the idea that maybe namin=
g a domain that isn&#39;t a good idea - or that in doing so you at least ne=
ed to learn the=C2=A0consequences.</div><div class=3D"gmail_default" style=
=3D"font-family:arial,helvetica,sans-serif"><br></div><div class=3D"gmail_d=
efault" style=3D"font-family:arial,helvetica,sans-serif">That, and given fe=
w complaints of this nature, and the fact we cannot at this point change th=
e policy that \d commands limit output based on visibility, means the easy =
fixes to deal with this specific complaint are unavailable even if they see=
m worthwhile (of which I have my doubts).</div><div class=3D"gmail_default"=
 style=3D"font-family:arial,helvetica,sans-serif"><br></div><div class=3D"g=
mail_default" style=3D"font-family:arial,helvetica,sans-serif">David J.</di=
v><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-se=
rif"><br></div></div></div>

--0000000000009f35ca064bd803a0--