Re: [PATCH] psql visibility clarification patch

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "D(dot) Hageman" <dhageman(at)dracken(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] psql visibility clarification patch
Date: 2003-01-24 05:33:00
Message-ID: 10531.1043386380@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

"D. Hageman" <dhageman(at)dracken(dot)com> writes:
> The goal of this patch is a solution to the issue that I found concerning
> table visibility. The problem with the way psql currently lists tables in
> a database is that it limits it to only the tables currently in the search
> path.

That's the intended behavior. I don't think that "\dt foo" should show
any tables other than the same "foo" you'd get from an unqualified
reference to "foo". If you want to know about foos that are not in
your search path, you can do "\dt *.foo".

Your proposed patch essentially eliminates the distinction between
\dt foo and \dt *.foo. This doesn't seem like a step forward to me.
Perhaps what's really needed is a documentation patch explaining when
to use each?

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message John Liu 2003-01-24 14:32:13 poor performance of subquery in psql
Previous Message Tom Lane 2003-01-24 05:23:55 pgsql-server/src/bin/psql Tag: REL7_3_STABLE c ...

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Clift 2003-01-24 05:42:33 Re: Release Scheduales: 7.2.4 & 7.3.2
Previous Message Tom Lane 2003-01-24 04:52:07 Re: Cast and Schemas don't work as expected