The following bug has been logged on the website:
Bug reference: 8150
Logged by: Erwin Brandstetter
Email address: brandstet...@falter.at
PostgreSQL version: 9.2.4
Operating system: Multiple
Description:
PostgreSQL allows to cast the result of unnest() directly. Howev
brandstet...@falter.at writes:
> SELECT unnest('{1,NULL,4}'::int[])::int8;
> i
> ---
> 1
> 4
Hm ... this seems to be a very old oversight in ExecMakeFunctionResult:
when it's dealing with a set-valued function argument, if the function
is strict and the particular input value is NULL, it sets t
On Sat, May 11, 2013 17:13, Tom Lane wrote:
> brandstet...@falter.at writes:
>> SELECT unnest('{1,NULL,4}'::int[])::int8;
>> i
>> ---
>> 1
>> 4
>
>
> This is another case where I'm not too sure if we ought to back-patch.
> The current behavior is clearly wrong, but perhaps some application
> out
