From: | 徐志宇徐 <xuzhiyuster(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: About psql \dt unable display same name table which have different schema |
Date: | 2022-05-24 16:39:00 |
Message-ID: | CAOCebiL1ycW++wXVJSak2DFqzaKi8Cqf16zOrt_9WL1j3vY3SQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Tom.
Thanks for your explanation. I got it.
I really appreciate it.
Jack Xu.
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> 于2022年5月25日周三 00:16写道:
> =?UTF-8?B?5b6Q5b+X5a6H5b6Q?= <xuzhiyuster(at)gmail(dot)com> writes:
> > I don't know why this problem exist. Why unable display both table "
> > public.test10 、 new. test10 "
>
> That's behaving as designed: \dt will show you tables that are
> accessible with an unqualified name, but new.test10 is hidden
> behind public.test10, so it's not accessible except by
> qualification.
>
> You can do "\dt *.*" or "\dt new.*", etc, to see such tables.
>
> See here for more info:
>
> https://www.postgresql.org/docs/current/app-psql.html#APP-PSQL-PATTERNS
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Aleš Zelený | 2022-05-24 18:16:42 | Pg14 possible index corruption after reindex concurrently |
Previous Message | Tom Lane | 2022-05-24 16:16:09 | Re: About psql \dt unable display same name table which have different schema |