Joe Conway <mail@joeconway.com> writes:
> Tom Lane wrote:
>> We could probably hack the inlining logic to prevent it from inlining
>> the function in this scenario, but I wonder whether this doesn't say
>> that ExecEvalArray is behaving inconsistently. In other operations, any
>> NULL in means NULL out. Shouldn't it simply quietly return a NULL array
>> if one of the supplied elements is NULL?
> That probably makes good sense, at least until we can deal with NULL
> elements. Would that patch count as a bug fix?
Either one would count as a bug fix IMHO. Anyone else have an opinion
on which to do?
regards, tom lane
