From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
Cc: | "Greg Sabino Mullane" <greg(at)turnstep(dot)com>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: Consistent \d commands in psql |
Date: | 2008-04-01 04:58:44 |
Message-ID: | 20510.1207025924@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Gregory Stark <stark(at)enterprisedb(dot)com> writes:
>>> One --perhaps nice, perhaps not-- property of this is that if you defined a
>>> function named "rtrim" and then did "\df rtrim" it would show you _both_ the
>>> system and user function and make it easier to see the conflict. Whereas the
>>> other behaviour I proposed would hide the system function which might
>>> exacerbate the user's confusion.
>> Another way we could approach this is
>> ...
> That doesn't satisfy the original source of the annoyance which is that \df
> spams your terminal with ten screens of system functions with your user
> functions hidden amongst them.
Sure, but I think the core objection there is that there is no easy way
to see only the user-defined functions. Given your point quoted first
above, I'm unconvinced that should be the default behavior.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Mathias Hasselmann | 2008-04-01 07:35:56 | Re: [HACKERS] Avahi support for Postgresql |
Previous Message | Alex Hunsaker | 2008-04-01 02:03:14 | Re: [PATCHES] [badalex@gmail.com: Re: [BUGS] Problem identifying constraints which should not be inherited] |