Skip to content

Commit b136db0

Browse files
committed
Fix planner's failure to identify multiple hashable ScalarArrayOpExprs
50e17ad (v14) and 29f45e2 (v15) made it so the planner could identify IN and NOT IN clauses which have Const lists as right-hand arguments and when an appropriate hash function is available for the data types, mark the ScalarArrayOpExpr as hashable so the executor could execute it more optimally by building and probing a hash table during expression evaluation. These commits both worked correctly when there was only a single ScalarArrayOpExpr in the given expression being processed by the planner, but when there were multiple, only the first was checked and any subsequent ones were not identified, which resulted in less optimal expression evaluation during query execution for all but the first found ScalarArrayOpExpr. Backpatch to 14, where 50e17ad was introduced. Author: David Geier <geidav.pg@gmail.com> Discussion: https://postgr.es/m/29a76f51-97b0-4c07-87b7-ec8e3b5345c9@gmail.com Backpatch-through: 14
1 parent 6c12ae0 commit b136db0

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/backend/optimizer/util/clauses.c

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2326,7 +2326,7 @@ convert_saop_to_hashed_saop_walker(Node *node, void *context)
23262326
/* Looks good. Fill in the hash functions */
23272327
saop->hashfuncid = lefthashfunc;
23282328
}
2329-
return true;
2329+
return false;
23302330
}
23312331
}
23322332
else /* !saop->useOr */
@@ -2364,7 +2364,7 @@ convert_saop_to_hashed_saop_walker(Node *node, void *context)
23642364
*/
23652365
saop->negfuncid = get_opcode(negator);
23662366
}
2367-
return true;
2367+
return false;
23682368
}
23692369
}
23702370
}

0 commit comments

Comments
 (0)