Re: RETURNS TABLE returns NULL set when called by another RETURNS TABLE

> val1 is just as ambiguous.  I think you got bit by the name collision;
> the output parameters would start out NULLs and thus lead to the
> described behavior, in versions before 9.0.

Aha, yeah, that's probably it.  Take this example as the reason we had
to change the behavior ...

--Josh Berkus