diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2012-01-02 14:43:51 -0500 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2012-01-02 14:43:51 -0500 |
commit | 188f1b928205bf33ce29887eeeee26ce9227908f (patch) | |
tree | 37b742f21a639411ff5c6e8d2bb8e9123bf53860 /src/include/postgres_ext.h | |
parent | 71b23708d4433d731082ed9c5ca491c7595e0e4d (diff) | |
download | postgresql-188f1b928205bf33ce29887eeeee26ce9227908f.tar.gz postgresql-188f1b928205bf33ce29887eeeee26ce9227908f.zip |
Fix coerce_to_target_type for coerce_type's klugy handling of COLLATE.
Because coerce_type recurses into the argument of a CollateExpr,
coerce_to_target_type's longstanding code for detecting whether coerce_type
had actually done anything (to wit, returned a different node than it
passed in) was broken in 9.1. This resulted in unexpected failures in
hide_coercion_node; which was not the latter's fault, since it's critical
that we never call it on anything that wasn't inserted by coerce_type.
(Else we might decide to "hide" a user-written function call.)
Fix by removing and replacing the CollateExpr in coerce_to_target_type
itself. This is all pretty ugly but I don't immediately see a way to make
it nicer.
Per report from Jean-Yves F. Barbier.
Diffstat (limited to 'src/include/postgres_ext.h')
0 files changed, 0 insertions, 0 deletions