| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Euler Taveira de Oliveira <euler(at)timbira(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: psql \d* and system objects |
| Date: | 2009-03-30 14:25:41 |
| Message-ID: | 603c8f070903300725i50714c15wf0e8056c47e2139d@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Mar 30, 2009 at 10:13 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Maybe the best we are going to do is to have any pattern supplied to \d*
> assume 'S' (include system objects). I actually have a patch that does
> that, attached. (It is from January so might need adjustment.)
That still has the problem that "\df a*" is horribly inconsistent with
"\df". It might be reasonable to assume that if a name without
wildcards is given to any \d command, it should display whatever
object it finds, user or system - but I can't see doing it for any
wildcard at all.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-03-30 14:29:15 | Re: psql \d* and system objects |
| Previous Message | Tom Lane | 2009-03-30 14:23:36 | Re: PQinitSSL broken in some use casesf |