Re: Unexpected omission of tables with duplicate names across schemas - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Unexpected omission of tables with duplicate names across schemas
Date
Msg-id 16656.1285694276@sss.pgh.pa.us
Whole thread Raw
In response to Unexpected omission of tables with duplicate names across schemas  (Chris Ross <cross@markmonitor.com>)
Responses Re: Unexpected omission of tables with duplicate names across schemas
List pgsql-bugs
Chris Ross <cross@markmonitor.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

pgsql-bugs by date:

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