Re: \dt doesn't show all relations in user's schemas (8.4.2)

From: Adrian Klaver <aklaver(at)comcast(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, Filip Rembiałkowski <plk(dot)zuber(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org, Ralph Graulich <ralph(dot)graulich(at)t-online(dot)de>
Subject: Re: \dt doesn't show all relations in user's schemas (8.4.2)
Date: 2009-12-22 00:00:21
Message-ID: 200912211600.21543.aklaver@comcast.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Monday 21 December 2009 3:42:10 pm Tom Lane wrote:
> Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> writes:
> > So, either the docs for \dt need fixing to reflect reality, or they're
> > right and psql \dt needs fixing.
>
> The documentation says
>
> 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 the pattern *.
> To see all objects in the database, use the pattern *.*.
>
> Seems clear enough to me.
>
> regards, tom lane

Well yes and no. The first couple of times I read this I was tripped up by
layout:
"the pattern *. To see all objects in the database, use the pattern *.*." I
took it to mean pattern '*.' until I realized it was '*' period. Taught me to
slow down when reading.

The other issue is what defines 'visible'. Previous investigations led me to:
"When there are objects of identical names in different schemas, the one found
first in the search path is used"
This is not obvious from the \d command explanation.

--
Adrian Klaver
aklaver(at)comcast(dot)net

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2009-12-22 00:24:13 Re: \dt doesn't show all relations in user's schemas (8.4.2)
Previous Message Tom Lane 2009-12-21 23:42:10 Re: \dt doesn't show all relations in user's schemas (8.4.2)