On Wed, Sep 29, 2010 at 2:19 PM, Chris Ross wrote:
> On 09/29/2010 02:08 PM, Chris Ross wrote:
>>
>> On 09/28/2010 01:17 PM, Tom Lane wrote:
>>>
>>> That's the intended behavior, because only the first one is actually
>>> accessible without schema-qualifying its name. You can use a pattern
>>> of
On 09/28/2010 01:17 PM, Tom Lane wrote:
Chris Ross 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+]. (Al
On 09/29/2010 02:08 PM, Chris Ross wrote:
On 09/28/2010 01:17 PM, Tom Lane wrote:
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
Chris Ross 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 int
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)
PostgreSQL versions: 8.2.x, 8.3.x, 8.4.4,
