From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | totocrenn(at)gmail(dot)com, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #14535: SET search_path and list tables |
Date: | 2017-02-08 16:04:54 |
Message-ID: | 1926.1486569894@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Wed, Feb 8, 2017 at 4:33 AM, <totocrenn(at)gmail(dot)com> wrote:
>> I have 2 SCHEMAS : test and demo
>> Each schemas have the same TABLE : table
>> So when I list all the tables with \dt I should have 2 tables : test.table
>> and demo.table, but I only see test.table.
> It is a choice - \dt, without a object schema specified, will show you the
> single object that would be chosen if you have written a query in a
> similar fashion:
> i.e., SELECT * FROM table;
If you want to see all occurrences of the table name, you can write
something like "\dt *.table". But without any schema component in the
pattern, psql's \d commands will only show objects that are visible in
the search path --- which means "they could be referenced by unqualified
names", not "their schema is in the search path someplace".
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-02-08 17:09:50 | Re: BUG #14526: no unique or exclusion constraint matching the ON CONFLICT |
Previous Message | Tiago Babo | 2017-02-08 15:30:38 | Re: BUG #14526: no unique or exclusion constraint matching the ON CONFLICT |