| 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-03-31 15:44:19 |
| Message-ID: | 28526.1206978259@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.
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2008-03-31 16:33:26 | Re: [PATCHES] Minimum selectivity estimate for LIKE 'prefix%' |
| Previous Message | Gregory Stark | 2008-03-31 15:34:23 | Re: Consistent \d commands in psql |