| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Tyler Kellen <tyler(at)sleekcode(dot)net>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #5838: tables of the same name in different schemas |
| Date: | 2011-01-14 17:51:53 |
| Message-ID: | 8217.1295027513@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
> On 14.01.2011 10:07, Tyler Kellen wrote:
>> Given two objects of the same name in different schemas, when both schemas
>> are in the search_path, \d only shows the object from the first schema
>> listed.
> That's intentional. \d lists the object that are currently visible in
> your search_path. The object in the schema that's later in search_path
> is being shadowed by the one in the first schema, so it's not visible.
You can use "\d *.*" if you want to see objects that are not visible
in the search path.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aren Cambre | 2011-01-15 03:32:05 | BUG #5839: pgAdmin makes bad query for creating a table when default value specified |
| Previous Message | Heikki Linnakangas | 2011-01-14 11:12:12 | Re: BUG #5838: tables of the same name in different schemas |