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:57:57 |
Message-ID: | 603c8f070903300757s5244f030ibd864fc84a7e0565@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Mar 30, 2009 at 10:52 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Robert Haas wrote:
>> 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.
>
> I think you are re-iterating the URL I referenced when I started this
> thread:
>
> http://archives.postgresql.org/pgsql-hackers/2009-01/msg01443.php
>
> I think the big question is whether the inconsistency (pattern implies
> 'S') is worth accepting for greater usability.
The inconsistency would be less objectionable if there were a way to
override it when it's not what you want.
...Robert
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Chernow | 2009-03-30 14:59:04 | Re: PQinitSSL broken in some use casesf |
Previous Message | Bruce Momjian | 2009-03-30 14:53:23 | Re: PQinitSSL broken in some use casesf |