Repository navigation
fix: match WHERE subquery by location - #2034
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
levkk
approved these changes
Nov 13, 2026
Contributor
|
Metal bench (arm64) passed. All 517 measures within bounds.
Counters per txn
Microbench: all 504 measures within bounds. Hot code per txn
pooler:
sharding-w2:
Logslb, microbench, pooler, sharding-w2, sharding-w8, verdict.json |
Contributor
|
Metal bench (x86) passed. All 517 measures within bounds.
Counters per txn
Microbench: all 504 measures within bounds. Hot code per txn
pooler:
sharding-w2:
Logslb, microbench, pooler, sharding-w2, sharding-w8, verdict.json |
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
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.
Previously, when we rewrote cross-shard subqueries in WHERE with the rows that those specific subqueries returned, we weren't checking which subquery we replaced, which caused all of the subqueries in WHERE to be replaced with these rows (even for other subqueries we weren't supposed to rewrite, causing incorrect response to be returned)
E.g., if we have a statement such as
The subquery is executed and rewritten for the
orderssubquery, however, it shouldn't be for thestatesone, asordersis sharded andstatesisn't. However, previously, both subqueries would be replaced with the user ids from theordersquery.Now, the subquery is matched by location in the statement, so only applicable subqueries are rewritten in this scenario.