Tom Lane wrote:
> Joe Conway <mail(at)joeconway(dot)com> writes:
>>Preference of extending FunctionCallInfoData or ReturnSetInfo?
> Definitely ReturnSetInfo. If we put it in FunctionCallInfoData then
> that's an extra word to zero for *every* fmgr function call, not only
> table functions.
+ TupleDesc queryDesc; /* descriptor for planned query */
to ReturnSetInfo, and populates ReturnSetInfo for every function call to
ExecMakeTableFunctionResult, not just when fn_retset.
> One thing to notice is that a table function that's depending on this
> info being available will have to punt if it's invoked via
> ExecMakeFunctionResult (ie, it's being called in a SELECT targetlist).
> That doesn't bother me too much, but maybe others will see it
I haven't done it yet, but I suppose this should be documented in
xfunc.sgml. With this patch the behavior of a function called through
ExecMakeFunctionResult will be:
ReturnSetInfo is populated but queryDesc is set to NULL
ReturnSetInfo is NULL
If there are no objections, please apply.
In response to
pgsql-hackers by date
|Next:||From: Joe Conway||Date: 2002-08-30 20:57:13|
|Subject: Re: Running postgres on a read-only file system|
|Previous:||From: Tyler Mitchell||Date: 2002-08-30 20:47:00|
|Subject: Running postgres on a read-only file system|