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

2010/2/24 Josh Berkus <josh@agliodbs.com>:
>
>> val1 is just as ambiguous. =C2=A0I think you got bit by the name collisi=
on;
>> 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. =C2=A0Take this example as the reason we h=
ad
> to change the behavior ...

yes - I am very happy with this change. It is the biggest change in
plpgsql over 10 years.

Pavel

>
> --Josh Berkus
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs
>