Re: Function parameter names
От
Tom Lane
Тема
Re: Function parameter names
Дата
Msg-id
28054.1069609149@sss.pgh.pa.us
Ответ на
Re: Function parameter names (Peter Eisentraut)
Список
Дерево обсуждения
Function parameter names Dennis Bjorklund <db@zigo.dhs.org>
Re: Function parameter names Peter Eisentraut <peter_e@gmx.net>
Re: Function parameter names Tom Lane <tgl@sss.pgh.pa.us>
Re: Function parameter names Dennis Bjorklund <db@zigo.dhs.org>
Re: Function parameter names Tom Lane <tgl@sss.pgh.pa.us>
Re: Function parameter names Dennis Bjorklund <db@zigo.dhs.org>
Re: Function parameter names Tom Lane <tgl@sss.pgh.pa.us>
Re: Function parameter names Dennis Bjorklund <db@zigo.dhs.org>
Re: Function parameter names Tom Lane <tgl@sss.pgh.pa.us>
Re: Function parameter names Neil Conway <neilc@samurai.com>
Re: Function parameter names Dennis Bjorklund <db@zigo.dhs.org>
Re: Function parameter names Tom Lane <tgl@sss.pgh.pa.us>
Re: Function parameter names Dennis Bjorklund <db@zigo.dhs.org>
Peter Eisentraut 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
В списке pgsql-hackers по дате отправления