-
-
Notifications
You must be signed in to change notification settings - Fork 238
[no-release-notes] Trace debugger for join planner, bug fix for Doltgres indexed joins #3289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…ing indexes for certain queries
| } | ||
|
|
||
| m.Tracer.Log("Starting cost-based optimization for groups %s", m) | ||
| if m.Tracer.TraceEnabled { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this check needed here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess not actually
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's remove it
This PR adds a new trace logging level to the Analyzer, which is only used in the join planning phase. Various new debug print methods are added to ExprGroup.
Adds an pseudo-extension point for SplitConjunction's use in join planning, which is necessary to properly detect the join conditions for use in indexes in Doltgres.
Finally, introduces several iterator methods for ExprGroup and related objects.