aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeHashjoin.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2012-10-11 12:20:56 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2012-10-11 12:22:13 -0400
commit4816d2ea3250b0f1e43d8b5521b9bf951821a945 (patch)
tree8ade90076fb7d33eea27bc61aafcfef75904311b /src/backend/executor/nodeHashjoin.c
parent6f60fdd7015b032bf49273c99f80913d57eac284 (diff)
downloadpostgresql-4816d2ea3250b0f1e43d8b5521b9bf951821a945.tar.gz
postgresql-4816d2ea3250b0f1e43d8b5521b9bf951821a945.zip
Fix cross-type case in partial row matching for hashed subplans.
When hashing a subplan like "WHERE (a, b) NOT IN (SELECT x, y FROM ...)", findPartialMatch() attempted to match rows using the hashtable's internal equality operators, which of course are for x and y's datatypes. What we need to use are the potentially cross-type operators for a=x, b=y, etc. Failure to do that leads to wrong answers or even crashes. The scope for problems is limited to cases where we have different types with compatible hash functions (else we'd not be using a hashed subplan), but for example int4 vs int8 can cause the problem. Per bug #7597 from Bo Jensen. This has been wrong since the hashed-subplan code was written, so patch all the way back.
Diffstat (limited to 'src/backend/executor/nodeHashjoin.c')
0 files changed, 0 insertions, 0 deletions