Re: Status of plperl inter-sp calling - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Status of plperl inter-sp calling
Date
Msg-id 4111.1262796106@sss.pgh.pa.us
Whole thread Raw
In response to Re: Status of plperl inter-sp calling  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Status of plperl inter-sp calling  (Bruce Momjian <bruce@momjian.us>)
Re: Status of plperl inter-sp calling  (Tim Bunce <Tim.Bunce@pobox.com>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> Next question: what do we do if a direct-called function calls 
> return_next()? That at least must surely take effect in the caller's 
> context - the callee won't have anywhere to stash the the results at all.

Whatever do you mean by "take effect in the caller's context"?  I surely
hope it's not "return the row to the caller's caller, who likely isn't
expecting anything of the kind".

I suspect Tim will just answer that he isn't going to try to
short-circuit the call path for set-returning functions.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Status of plperl inter-sp calling
Next
From: Tom Lane
Date:
Subject: Re: 'replication' keyword on .pgpass (Streaming Replication)