From: | "Greg Sabino Mullane" <greg(at)turnstep(dot)com> |
---|---|
To: | pgsql-patches(at)postgresql(dot)org |
Subject: | Re: Consistent \d commands in psql |
Date: | 2008-04-02 13:17:52 |
Message-ID: | 27d0a5b6bcbe8c800d086429e43bf334@biglumber.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
> \df Lists all user functions
> \df [pattern] Lists both system and user functions matching [pattern]
> \df * Lists all system and user functions
I don't like this for two reasons: the items returned changes based on
the existence of args, rather than on the command itself, and more
importantly, this would make it inconsistent with the other backslash
commands.
> One question: should \df really list *all* nonsystem functions? Or just
> the ones that are visible in your search path? I'd be inclined to say
> the second.
Agreed, we should respect the search path like the other commands do.
Although I wonder if a long-term idea would be to at least indicate
that there are other same-named things in your path?
- --
Greg Sabino Mullane greg(at)endpoint(dot)com greg(at)turnstep(dot)com
End Point Corporation 610-983-9073
PGP Key: 0x14964AC8 200804020915
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iEYEAREDAAYFAkfzh0IACgkQvJuQZxSWSsgTCgCdEv1vl7c0uIpIU3pSiH/VLvEg
m5wAni5/gJ0K2w1gpaNaWpVFCRJX200f
=ZnTm
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-04-02 15:40:19 | Re: Consistent \d commands in psql |
Previous Message | Greg Sabino Mullane | 2008-04-02 12:55:40 | Re: Friendly help for psql |