| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Function parameter names |
| Date: | 2003-11-23 17:39:09 |
| Message-ID: | 28054.1069609149@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Dennis Bjorklund writes:
>> I'm in the middle of implementing function parameter names.
> So these two reasons make a "namevector" impractical: First, it would
> probably not be in the performance critical path. Second, it would use up
> a fixed length of NAMEDATALEN * FUNC_MAX_ARGS (currently 1024 bytes) in
> every pg_proc row. In this case, a regular name[] would be more suitable.
> Just be sure to put it after all the fixed-length fields.
Actually I'd suggest text[], as there is no good reason to pad the
array entries to a fixed length.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2003-11-23 18:17:19 | initdb mkdir_p() doesn't work |
| Previous Message | Peter Eisentraut | 2003-11-23 17:19:19 | Re: Function parameter names |