Instrument plan creation #36
Draft
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
geoffreyclaude
force-pushed
the
feat/instrument_plan_creation
branch
4 times, most recently
from
f5b14b0 to
4230ce8
Compare
Introduces TracingQueryPlanner and rule instrumentation for analyzer, logical optimizer, and physical optimizer rules with tracing spans. Phase spans group individual rule executions and capture plan diffs when rules modify plans. Ergonomic API via RuleInstrumentationOptions::full() and instrument_rules_with_info_spans! macro.
geoffreyclaude
force-pushed
the
feat/instrument_plan_creation
branch
from
4230ce8 to
94b89d6
Compare
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.
Which issue does this PR close?
Rationale for this change
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?