Jan -- Anyone who trades liberty for security deserves neither liberty nor security. -- Benjamin Franklin -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
I am aware that in the case at hand, the call to make_fn_arguments() is
with the only possible candidate function, so changing COERCE_IMPLICIT
to COERCE_ASSIGNMENT inside of make_fn_arguments() is correct. But I
wonder if this may have any unwanted side effects for other code paths
to make_fn_arguments(), like from optimizer/util/clauses.c or from
parser/parse_oper.c. I'm not saying it does, just asking if that could
be the case.
- Re: [HACKERS] MySQL search query is not executing in Postgre... Jan Wieck
- Re: [HACKERS] MySQL search query is not executing in Po... Robert Haas
- Re: [HACKERS] MySQL search query is not executing i... Pavel Stehule
- Re: [HACKERS] MySQL search query is not executing i... Jeff Davis
- Re: [HACKERS] MySQL search query is not executi... Darren Duncan
- Re: [HACKERS] MySQL search query is not executi... Robert Haas
- Re: [HACKERS] MySQL search query is not exe... Tom Lane
- Re: [HACKERS] MySQL search query is no... Robert Haas
- Re: [HACKERS] MySQL search query i... Jan Wieck
- Re: [HACKERS] MySQL search query is not executing in Po... Jeff Davis
- Re: [HACKERS] MySQL search query is not executing in Po... Jeff Davis