postgres_exporter got updated to 0.15.0, closing critical issue with exhausting of the server pool connections. #864
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
exhausting of the server pool connections.
|
Ok, apparently this duplicates #863, but it's not a minor update - the 0.14.0 version created issues on our production boxes by taking over all the available connections from the connections pool. (yes, there are ways to avoid it, but was quite unexpected). |
|
@b-a-t, thanks, it's merged and RPM packages should be available in about 10-15 minutes. |
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.
[ENHANCEMENT] Add 1kB and 2kB units prometheus-community/postgres_exporter#915
[BUGFIX] Add error log when probe collector creation fails prometheus-community/postgres_exporter#918
[BUGFIX] Fix test build failures on 32-bit arch prometheus-community/postgres_exporter#919
[BUGFIX] Adjust collector to use separate connection per scrape prometheus-community/postgres_exporter#936
That last one created a lot of issues for some deployments.