Peter Eisentraut <peter_e@gmx.net> writes:
> In the presence of a comma-separated list of arguments it seems to
> intepret the EXECUTE command wildly differently. What is going on here?
Basically it evaluates the string-producing argument by sticking SELECT
on the front and handing it to the main SQL engine. So what you've got
there is a SELECT that produces two result columns, where the EXECUTE
code was only expecting to get one. (Look at exec_eval_expr in pl_exec.c)
It's a syntax error in any case; not sure if we can easily produce a
better error message, or what a better error message would be.
regards, tom lane
