Re: Unexpected omission of tables with duplicate names across schemas

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Chris Ross <cross(at)markmonitor(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org, Chris Ross <chris(dot)ross(at)markmonitor(dot)com>
Subject: Re: Unexpected omission of tables with duplicate names across schemas
Date: 2010-09-28 17:17:56
Message-ID: 16656.1285694276@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Chris Ross <cross(at)markmonitor(dot)com> writes:
> When there is a table (or view, or sequence) of the same name in one
> schema as another, and both of these schemas are in the set search_path,
> only the first schema in the search path will show that name in the
> output of \d[S+]. (Also \dt, \dv, etc)

That's the intended behavior, because only the first one is actually
accessible without schema-qualifying its name. You can use a pattern
of "*.*" if you want to see objects that are hidden according to the
search path. The default behavior is equivalent to a pattern of "*",
which only shows objects reachable with unqualified names.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2010-09-28 18:24:15 Re: LEFT OUTER JOIN sub-SELECT produces a column != NULL when all NULLs are expected
Previous Message Chris Ross 2010-09-28 16:58:15 Unexpected omission of tables with duplicate names across schemas