* Tom Lane (t...@sss.pgh.pa.us) wrote: > Dunno, I think that's going to result in a very large chunk of mostly > duplicative code in psql. regprocedurein() is fairly short because it > can rely on a ton of code from the parser, but psql won't have that > luxury.
Parsing/tokenizing a CSV string inside parens doesn't strike me as all that difficult, even when handling the space-delimininated varname from the type. The hard part would, I think, be the normalization of the type names into what \df returns, but do we even want to try and tackle that..?. How much do we care about supporting every textual representation of the 'integer' type? That's not going to be an issue for people doing tab-completion or using \df's output. We could also have it fall-back to trying w/o any arguments for a unique function name match if the initial attempt w/ the function arguments included doesn't return any results. Thanks, Stephen
signature.asc
Description: Digital signature