Andrew Dunstan <and...@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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers