This repository has been archived by the owner on Sep 4, 2021. It is now read-only.
appliance/postgresql: Don’t log transaction errors #2741
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
The default log level is ERROR which logs transaction errors to the pg log. These errors are also provided to the client, which can log them if they are relevant. Log messages that admins care about will have level of LOG or higher. Closes #2739 Signed-off-by: Jonathan Rudenberg <jonathan@titanous.com>
|
LGTM |
1 similar comment
|
LGTM |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The default log level is
ERRORwhich logs transaction errors to the pg log. These errors are also provided to the client, which can log them if they are relevant. Log messages that admins care about will have level ofLOGor higher.Closes #2739