Add query execution plan to sql_detail #452
Merged
Conversation
This file contains 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.
This PR aims to collect query execution plan details with a visualization into the sql detail tab.
Having quick details of the execution plan can be very useful when debugging subtle issues like indexes usage and so on.
The explain feature is supported by all builtin databases except for Oracle, so a feature check is performed and if it fails the collection is skipped and the Query Plan section is not rendered.
It also adds a config key called
SILKY_ANALYZE_QUERIESwhich can be set toTruein order to enable theANALYZEflag, which provides more detailed information about the query execution.That said, thank you for your efforts in this great project!