Parameterized query plans#5287
Open
joshua-spacetime wants to merge 1 commit into
Open
Conversation
Base automatically changed from
joshua/refactor/subscription-plan-cache
to
master
June 12, 2026 14:42
joshua-spacetime
force-pushed
the
joshua/params-and-bind-vars
branch
from
5e6ad1e to
c90f4ed
Compare
joshua-spacetime
force-pushed
the
joshua/params-and-bind-vars
branch
from
f3fdb25 to
f6d510a
Compare
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
1 participant
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
Makes runtime parameters explicit in query plans (prerequisite for parameterized views).
As part of this change,
senderis no longer baked directly into query plans as a literal value. Instead it is represented as a parameter in the query plan. Values are supplied at runtime via a variable environment calledExecutionParams.Note, parameterized plans are still not shared across subscriptions yet. That will be done in a follow up.
This is mostly a mechanical change. The majority of the diff is just threading runtime params/variables through various call sites.
API and ABI breaking changes
N/A
Expected complexity level and risk
...
Testing
Existing coverage