Tom,
Thanks a lot.
The part I cant understand is I cant see where SendFunctionResult construct
the return value into the buf. I expect it should copy something in retval
to buf, but I cant find any of this in the code, the main logic of
SendFunctionResult is:
00159 getTypeOutputInfo
lee Richard writes:
> I still can not see how it return a single return value to the client, and
> why it call FunctionCall1() again when it want to send the result.
pq_endmessage is where the bytes actually get pushed out to the client,
if that's what you're looking for. The rest of the activit
Merlin,
Oh, I didnt realized that it does not support to return scalar, thanks a
lot.
When it returns a single value, I see it use the following function,
SendFunctionCall
result = DatumGetByteaP(FunctionCall1(flinfo, val));
I still can not see how it return a single return value to the
On Sun, May 8, 2011 at 8:01 AM, lee Richard wrote:
> Hi,
>
> I am reading the source code of fastpath to understand the internal of
> fastpath. I can not understand how does it send result to the client, I hope
> somebody can help me on this.
>
> I see it call it invoke the function in
>
> HandleF
Hi,
I am reading the source code of fastpath to understand the internal of
fastpath. I can not understand how does it send result to the client, I hope
somebody can help me on this.
I see it call it invoke the function in
HandleFunctionRequest()
-> retval = FunctionCallInvoke(&fcinfo);
-> Se
