| From: | "Merlin Moncure" <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | "David Fetter" <david(at)fetter(dot)org> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Timothy Perrigo" <tperrigo(at)wernervas(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: getting function argument names from psql? |
| Date: | 2006-07-13 13:22:56 |
| Message-ID: | b42b73150607130622n344b7d48o183ebffb98b2137e@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 7/13/06, David Fetter <david(at)fetter(dot)org> wrote:
> On Wed, Jul 12, 2006 at 11:37:04PM -0400, Tom Lane wrote:
> > > select oid::regprocedure from pg_proc where proname like 'your
> > > name here';
> >
> > Nope, because regprocedureout doesn't include argument names (nor
> > modes). I think the best way ATM is to look directly at
> > pg_proc.proargnames :-(
whoop! misread it :)
> Back when, I submitted a psql patch to get the input names along with
> their types. Shall I dig up that code this weekend?
that would be great, although is there any concern about backwards
compatibility of regprocedure cast? would it be safer to make a new
cast? also, does your patch account for in/out?
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2006-07-13 13:30:49 | Re: getting function argument names from psql? |
| Previous Message | Merlin Moncure | 2006-07-13 13:20:51 | Re: Performance problem with query |