fix(db): Log long transaction times at debug level #45506
Merged
+2
−2
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
Signed-off-by: Josh <josh.t.richards@gmail.com>
joshtrichards
requested review from
ChristophWurst,
Altahrim,
juliushaertl and
szaimen
|
/backport to stable29 |
szaimen
approved these changes
May 25, 2024
Altahrim
approved these changes
May 27, 2024
This comment was marked as off-topic.
This comment was marked as off-topic.
Merged
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.
Summary
This was added as part of #42345. Per the implementation docs (plus what seems reasonable for non-dev/troubleshooting situations), these should not be logged at WARN level.
The PR's docs (nextcloud/documentation#11492) say DEBUG level. I suggest either DEBUG or, at most, INFO. I lean towards DEBUG so that's what I went with.
TODO
Checklist