We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We could expose total CPU planning time in QueryStats. This would simplify debugging planning issues and latency.
QueryStats
The text was updated successfully, but these errors were encountered:
Hello, I would love to try on this work. Thanks!
Sorry, something went wrong.
Sure, go ahead
@sopel39 Hi I think this stat will be useful. Can I continue on this?
Sure @weijiii
weijiii
Successfully merging a pull request may close this issue.
We could expose total CPU planning time in
QueryStats
. This would simplify debugging planning issues and latency.The text was updated successfully, but these errors were encountered: