aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/operatorcmds.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2011-11-17 18:28:41 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2011-11-17 18:28:41 -0500
commit1a8b9fb5499d8646661a57edd3c88c3107622ff8 (patch)
tree2d4d1683f2858d4a01b8f16a38eb324547c5d342 /src/backend/commands/operatorcmds.c
parentbf4f96b5e264f1c0f5d8694f11c6f9f5b3132b3b (diff)
downloadpostgresql-1a8b9fb5499d8646661a57edd3c88c3107622ff8.tar.gz
postgresql-1a8b9fb5499d8646661a57edd3c88c3107622ff8.zip
Extend the unknowns-are-same-as-known-inputs type resolution heuristic.
For a very long time, one of the parser's heuristics for resolving ambiguous operator calls has been to assume that unknown-type literals are of the same type as the other input (if it's known). However, this was only used in the first step of quickly checking for an exact-types match, and thus did not help in resolving matches that require coercion, such as matches to polymorphic operators. As we add more polymorphic operators, this becomes more of a problem. This patch adds another use of the same heuristic as a last-ditch check before failing to resolve an ambiguous operator or function call. In particular this will let us define the range inclusion operator in a less limited way (to come in a follow-on patch).
Diffstat (limited to 'src/backend/commands/operatorcmds.c')
0 files changed, 0 insertions, 0 deletions