Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> 2010/2/9 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>> I don't think this is right at all.
> yes, this isn't clear. My arguments for change:
> a) the behave depends on types - "any" is different than others.
So what? "variadic any" is different in a lot of ways.
> b) optimization over fmgr doesn't work now.
> b1. some possible const null and strict are ignored
That's a matter of definition.
> b2. array is non const always - so pre eval doesn't work for variadic
You'd need to explain what you mean by that. An ARRAY[] construct is
subject to const-folding AFAICS.
regards, tom lane