| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>, "David E(dot) Wheeler" <david(at)kineticode(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Status of plperl inter-sp calling |
| Date: | 2010-01-06 17:49:53 |
| Message-ID: | 201001061749.o06HnrZ16946@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)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.
FYI, I am excited PL/Perl is getting a good review and cleaning by Tim.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-01-06 17:54:43 | Re: fastgetattr & isNull |
| Previous Message | Stefan Kaltenbrunner | 2010-01-06 17:42:29 | snapshot generation broken again... |