Re: SRFs ExecMakeTableFunctionResult

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: James William Pye <flaw(at)rhid(dot)com>
Cc: Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SRFs ExecMakeTableFunctionResult
Date: 2004-08-09 14:25:55
Message-ID: 14433.1092061555@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

James William Pye <flaw(at)rhid(dot)com> writes:
> While I was finishing up SRF support in PL/Py, I noticed that when VPC is the
> selected mode for a table function, ExecMakeTableFunctionResult will set
> rsinfo.isDone to ExprSingleResult each time it loops to fetch another value
> (when a direct_function_call). This makes the VPC-SRF author set isDone to
> ExprMultipleResult on _every_ call while returning values, as it will break
> out if rsinfo.isDone !=3D ExprMultipleResult.

> Is this the desired behavior?

Seems reasonable to me. A SRF function really ought to explicitly set
isDone on every call anyway.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-08-09 14:32:54 Re: Changing the type of timestamp columns
Previous Message Tom Lane 2004-08-09 14:13:25 Re: 8.0.0beta1 ... packaged for testing ...