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

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Adrian Klaver <aklaver(at)comcast(dot)net>, 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 01:06:12
Message-ID: dcc563d10912211706q7f1550admfbf59d99f44835d@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Dec 21, 2009 at 4:42 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> 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.

Then you should see BOTH tables with the same name in different
schemas, right? Cause the OP was saying that it picks only the first
one to display.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2009-12-22 01:10:59 Re: \dt doesn't show all relations in user's schemas (8.4.2)
Previous Message Robert Hodges 2009-12-22 00:47:42 Re: Justifying a PG over MySQL approach to a project