Re: BUG #5838: tables of the same name in different schemas

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Tyler Kellen <tyler(at)sleekcode(dot)net>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5838: tables of the same name in different schemas
Date: 2011-01-14 11:12:12
Message-ID: 4D302F8C.3010800@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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.
>
> Reproduction:
> CREATE SCHEMA s1;
> CREATE SCHEMA s2;
> CREATE TABLE s1.test ( id int );
> CREATE TABLE s2.test ( id int );
> SET search_path TO s1,s2;
> \d
> SET search_path TO s2,s1;
> \d

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.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2011-01-14 17:51:53 Re: BUG #5838: tables of the same name in different schemas
Previous Message Tyler Kellen 2011-01-14 08:07:25 BUG #5838: tables of the same name in different schemas