Refactor extracting expressions for dynamic index scans #18095
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MARK join to SEMI in InClauseRewriter|
Thanks! |
krlmlr
added a commit
to krlmlr/duckdb-r
that referenced
this pull request
Jul 9, 2025
Refactor extracting expressions for dynamic index scans (duckdb/duckdb#18095) Cleanup on correct branch (1.3-ossivalis) instead of v1.2-histrionicus (duckdb/duckdb#18111)
krlmlr
added a commit
to krlmlr/duckdb-r
that referenced
this pull request
Jul 9, 2025
Refactor extracting expressions for dynamic index scans (duckdb/duckdb#18095) Cleanup on correct branch (1.3-ossivalis) instead of v1.2-histrionicus (duckdb/duckdb#18111)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I was looking into https://github.com/duckdblabs/duckdb-internal/issues/5049 and tried converting some of our
MARKjoins toSEMIjoins. This didn't fix the issue I was looking at (and regressed the IMDB benchmark, so I reverted it), but it uncovered a bug in the dynamic index scan (which I accidentally introduced in #17297). This PR cleans up the recursion through the nestedANDfilters and simplifies the logic so it's a lot less error-prone.I have tried, but can't seem to reproduce it without changing the
MARKtoSEMI. However, I still think the changes here are important as they fix a bug with complex filters that can trigger an index scan.