Re: Unexpected behavior from psql - Mailing list pgsql-general

From Jeff Davis
Subject Re: Unexpected behavior from psql
Date
Msg-id 1231713684.32466.4.camel@jdavis
Whole thread Raw
In response to Unexpected behavior from psql  (Tim Hart <tjhart@mac.com>)
Responses Re: Unexpected behavior from psql  (Tim Hart <tjhart@mac.com>)
List pgsql-general
On Sun, 2009-01-11 at 15:33 -0600, Tim Hart wrote:
> tjhart=# set search_path to foo, public;
> SET
> tjhart=# \d
>            List of relations
>   Schema |   Name    | Type  | Owner
> --------+-----------+-------+--------
>   foo    | bar_table | table | tjhart
>   foo    | foo_table | table | tjhart
> (2 rows)
>
> tjhart=# set search_path to public, foo;
> SET
> tjhart=# \d
>            List of relations
>   Schema |   Name    | Type  | Owner
> --------+-----------+-------+--------
>   foo    | bar_table | table | tjhart
>   public | foo_table | table | tjhart
> (2 rows)

This behavior seems consistent to me. If you type an unqualified name
like:

SELECT * FROM foo_table;

You'll get the one from the first namespace listed in search_path. It
makes sense for "\d" to display only the tables that can be seen without
specifying a fully-qualified name.

Regards,
    Jeff Davis


pgsql-general by date:

Previous
From: Tim Hart
Date:
Subject: Unexpected behavior from psql
Next
From: Tim Hart
Date:
Subject: Re: Unexpected behavior from psql