2010/2/9 Tom Lane <t...@sss.pgh.pa.us>: > Pavel Stehule <pavel.steh...@gmail.com> writes: >> + /* >> + * If function has variadic argument, skip calling >> + * when variadic array contains NULL values. >> + */ > > I don't think this is right at all. The strict check ought to apply to > the array argument as a whole.
yes, this isn't clear. My arguments for change: a) the behave depends on types - "any" is different than others. b) optimization over fmgr doesn't work now. b1. some possible const null and strict are ignored b2. array is non const always - so pre eval doesn't work for variadic c) it could be confusing, and it is partially confusing. point c could be solved by notice in documentation. But a and b are problem. The variadic funcall cannot be optimized :( Regards Pavel Stehule > > regards, tom lane > -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers