DOC-9438 Document overhead associated with sql.trace.log_statement_execute setting #18257
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
✅ Deploy Preview for cockroachdb-api-docs canceled.
|
✅ Deploy Preview for cockroachdb-interactivetutorials-docs canceled.
|
✅ Netlify Preview
To edit notification comments on pull requests, go to your Netlify site configuration. |
rmloveland
approved these changes
Feb 16, 2024
There was a problem hiding this comment.
LGTM
According to our release support policy we're supporting v22.2 until June 2024
if this info also applies to v22.2, suggest adding it to those docs also
…nabling sql.trace.log_statement_execute cluster setting will incur overhead.
florence-crl
force-pushed
the
DOC-9438
branch
from
f7748d1
to
81c4d9d
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.
Fixes DOC-9438
On Logging Overview and Logging Use Cases pages, added Warning that enabling sql.trace.log_statement_execute cluster setting will incur overhead.