| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] Improved \df(+) in psql + backward-compatibility |
| Date: | 2005-08-29 15:13:29 |
| Message-ID: | 10046.1125328409@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
David Fetter <david(at)fetter(dot)org> writes:
> I've noticed that \df doesn't do quite what it might when a function
> is created with named input parameters. Please find enclosed a patch
> against CVS TIP that does this better.
Meanwhile, getting back to the actual merits of the patch ... this is
not right yet, because it will do the wrong thing when there are OUT
parameters. (The proargnames array includes both IN and OUT params,
and you can't assume that proargnames and proargtypes have corresponding
subscripts.) It would probably be a good idea to discuss what display
we want for a function with OUT parameters, anyway. The strict columnar
representation that \df currently uses doesn't scale very well :-(
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2005-08-29 15:18:56 | Re: Win32 Thread safetyness |
| Previous Message | Sergey E. Koposov | 2005-08-29 15:09:00 | Re: 8.1beta, SunOS and shmget |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2005-08-29 15:36:55 | Re: [HACKERS] Improved \df(+) in psql + backward-compatibility |
| Previous Message | Andrew Dunstan | 2005-08-29 15:07:20 | Re: Improved \df(+) in psql + backward-compatibility |