From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Greg Sabino Mullane" <greg(at)turnstep(dot)com>, <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: Consistent \d commands in psql |
Date: | 2008-03-31 21:51:09 |
Message-ID: | 87abke8svm.fsf@oxford.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> 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.
>
> Yeah, that is a very good point indeed.
>
> Another way we could approach this is
>
> \df -> all functions
> \dfS -> sys functions only
> \dfU -> user functions only
>
> which avoids falling into the trap Greg mentions.
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.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS support!
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Hunsaker | 2008-04-01 02:03:14 | Re: [PATCHES] [badalex@gmail.com: Re: [BUGS] Problem identifying constraints which should not be inherited] |
Previous Message | Alvaro Herrera | 2008-03-31 21:36:29 | Re: Consistent \d commands in psql |