Prune more queries when evaluating subscription updates#2855
Merged
joshua-spacetime merged 4 commits intoJun 14, 2025
Conversation
joshua-spacetime
force-pushed
the
joshua/perf/more-query-pruning-for-joins
branch
from
8e0b0b6 to
e44323e
Compare
mamcx
suggested changes
Jun 12, 2025
Co-authored-by: Mario Montoya <mamcx@elmalabarista.com> Signed-off-by: joshua-spacetime <josh@clockworklabs.io>
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
2 participants
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.
Description of Changes
If a table is subscribed to, and it joins with many different tables, this optimization will attempt to prune joins that it knows are empty.
API and ABI breaking changes
None
Expected complexity level and risk
3
A bug will most likely result in incorrect subscription results
Testing