fix: run logical optimizer rules for TableScan expressions
#4614
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.
Which issue does this PR close?
Doesn't close any, but is related to #4370.
Rationale for this change
While working on #4370 I've discovered that we don't optimize expressions within
TableScannodes.What changes are included in this PR?
Include
TableScanexpressions within the logical optimization.Are these changes tested?
See plan change in
tpch_q22_correlated.Are there any user-facing changes?
Better optimized plans.