From: | Martin Pihlak <martin(dot)pihlak(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: psql \d commands and information_schema |
Date: | 2009-04-08 07:04:30 |
Message-ID: | 49DC4C7E.4090000@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Well, if they're all in your search_path then plain old \df will do
> fine. If they're not in your search path then I think it gets pretty
> questionable whether they're "user defined" in a real sense. It seems
> more likely that you've got a pile of modules loaded, and which of those
> modules is "user defined" for your immediate purposes is something that
> psql can't hope to intuit.
>
I my environment schemas are used for namespace separation, so it doesn't
make much sense to use search_path to pull everything back into a single
namespace. Might as well use public for everything then. And these are not
really modules, just ordinary user objects in separate namespaces.
The main benefit of the U switch is that it enables to get a quick overview
of whats deployed to the database. At the moment this is not possible as the
*.* listings are polluted with system objects.
PS. The original \dfU suggestion was made by you in
http://archives.postgresql.org/message-id/28027.1206976227@sss.pgh.pa.us.
And seems, it didn't receive too much negative feedback then.
regards,
Martin
From | Date | Subject | |
---|---|---|---|
Next Message | John Lister | 2009-04-08 07:12:13 | Re: Array types |
Previous Message | higepon | 2009-04-08 06:48:06 | Re: Auto-delete large objects when referencing row is deleted |