Re: psql \d command hides objects from "lower" schemas

From: Josh Kupershmidt <schmiddy(at)gmail(dot)com>
To: Ben Morgan <neembi(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: psql \d command hides objects from "lower" schemas
Date: 2013-01-23 16:11:49
Message-ID: CAK3UJRGeH0YS7kpDDB=kXXJ0_536E=t_x1axuHPT4dwdNmqQ4w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Jan 23, 2013 at 6:21 AM, Ben Morgan <neembi(at)gmail(dot)com> wrote:
> Given this, when using the psql command \d, I expect to see all the tables,
> and the view as well as the table. But instead the objects in the front-most
> schema mask the other objects.
>
> I'm submitting this as a bug, because it seems to be one. If this behavior
> is intended, please forgive me! (And if it is intended, is there flag to
> make objects in higher schemas not mask other objects?)

I think the relevant section of the docs:
http://www.postgresql.org/docs/current/static/app-psql.html

is the paragraph beginning:

| Whenever the pattern parameter is omitted completely, the \d commands
| display all objects that are visible in the current schema search
| path — this is equivalent to using * as the pattern.

Note, I believe that explanation is a bit lacking, i.e a plain.
\d
is quite different from
\d *
both in the format of the output, and that the latter displays
pg_catalog tables. At any rate, you can use:
\dtv *.*
for all tables and views in all schemas. (Unfortunately, you are then
stuck with noise from pg_catalog and information_schema.)

Josh

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alexander Law 2013-01-23 17:06:01 Re: BUG #6510: A simple prompt is displayed using wrong charset
Previous Message Kevin Grittner 2013-01-23 13:41:50 Re: BUG #7821: constant disconnection with external network