Re: \dt doesn't show all relations in user's schemas (8.4.2) - Mailing list pgsql-general

From Scott Marlowe
Subject Re: \dt doesn't show all relations in user's schemas (8.4.2)
Date
Msg-id dcc563d10912211717u43016ff2l3d8483bfdfb4b3a7@mail.gmail.com
Whole thread Raw
In response to Re: \dt doesn't show all relations in user's schemas (8.4.2)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: \dt doesn't show all relations in user's schemas (8.4.2)  (Adrian Klaver <aklaver@comcast.net>)
Re: \dt doesn't show all relations in user's schemas (8.4.2)  (Filip Rembiałkowski <plk.zuber@gmail.com>)
List pgsql-general
On Mon, Dec 21, 2009 at 6:14 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Scott Marlowe <scott.marlowe@gmail.com> writes:
>> On Mon, Dec 21, 2009 at 6:10 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> Well, yes, because only the first one is visible.  The second one is
>>> masked by the first.
>
>> But the docs say that ALL objects in the schema path will be shown.
>> So, my point stands, either the docs are wrong, or the behaviour is.
>> I'd think it's the docs.
>
> It says the *visible* objects will be shown.  Ones that are masked
> aren't any more visible than if they were in some other schema
> altogether: either way, if you want to reference such an object in
> a SQL statement, you'd have to schema-qualify it.

Ahh, right, it's about visibility.  Hadn't caught that part.

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: \dt doesn't show all relations in user's schemas (8.4.2)
Next
From: Adrian Klaver
Date:
Subject: Re: \dt doesn't show all relations in user's schemas (8.4.2)