release-20.2: opt: allow IN subquery to be converted to lookup join #63869
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport 2/2 commits from #63780.
/cc @cockroachdb/release
opt: add opttester facility to test placeholder assignment
We like to assume that the result of building a memo with placeholders
followed by AssignPlaceholders is equivalent to building the query
with the values directly. This is not necessarily the case - it is
possible that some normalization rules act on a higher part of the
tree in a way that would not happen if we had fully normalized a lower
part of the tree.
This commit adds two new opttester directives:
assign-placeholders-norm
andassign-placeholders-opt
. These take aquery that has placeholders and simulates the prepared query planning
path.
We use these facilities to add some tests that reproduce a customer
issue.
Release note: None
opt: allow IN subquery to be converted to lookup join
This change adds a rule that handles a case which prevents Exists
subqueries from becoming lookup joins.
Fixes #43198.
Release note (performance improvement): certain queries containing
<tuple> IN (<subquery>)
conditions may run significantly faster.