> > What I'd be inclined to think about is making > check_generic_type_consistency and related functions allow the > arguments matched to ANYELEMENT to be of different actual types > so long as select_common_type could determine a unique type to > coerce them all to. It'd take some refactoring (notably, because > select_common_type wants to throw error on failure, and because > there'd have to be a way to pass back the type that was selected > for use later).
+1 it's same like current implementation coalesce, least, greatest functions, thats works well. And with this change and with variatic functions we can move these functions from parser. 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 > -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
