Consider interpreting a function call as a trivial (binary-compatible)
Tom Lane <tgl@sss.pgh.pa.us>
Consider interpreting a function call as a trivial (binary-compatible) type coercion after failing to find an exact match in pg_proc, but before considering interpretations that involve a function call with one or more argument type coercions. This avoids surprises wherein what looks like a type coercion is interpreted as coercing to some third type and then to the destination type, as in Dave Blasby's bug report of 3-Oct-01. See subsequent discussion in pghackers.
Files
| Path | Change | +/− |
|---|---|---|
| doc/src/sgml/typeconv.sgml | modified | +11 −11 |
| src/backend/commands/indexcmds.c | modified | +14 −4 |
| src/backend/parser/parse_func.c | modified | +80 −65 |
| src/include/parser/parse_func.h | modified | +14 −4 |