Make sec-since-oldest-xact-start metric database-specific
#24
Conversation
This file contains hidden or 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
volodymyrpavlenko
force-pushed
the
get_oldest_transaction_timestamp_per_database
branch
from
4c17555 to
5bb8169
Compare
volodymyrpavlenko
deleted the
get_oldest_transaction_timestamp_per_database
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 fixes a bug, where
sec-since-oldest-xact-startis only reported for one largest transaction per monitored postgresql instance. This can lead to a situation, where spurious databases appear in metrics, and not more than 1 database is reported at every iteration.We would like to add database comparison name with the currently connected database. Since postgresql connects to every monitored database separately, this will effectively output
sec-since-oldest-xact-startmetrics per connected database.