feat: drop support for PG9.6 and PG10. simplify common queries. #322
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.
Description
Drop support for PostgreSQL 9.6 and 10 per the support statement in docs (https://access.crunchydata.com/documentation/pgmonitor/latest/#postgesql)
Now that 9.6 is dropped, many queries that required being in version specific query files can be moved to the global query file. Re-organized common vs version specific queries in docs.
Bugfix: Included improved replica replay monitoring metric discussed in Issue #319
Please indicate what kind of change your PR includes (multiple selections are acceptable):
PRs should be against existing issues, so please list each issue using a separate 'closes' line:
closes #319
Testing
None of the testing listed below is optional.
Code testing
Have you tested your changes against:
If your code touches postgres_exporter, have you:
If your code touches node_exporter, have you:
If your code touches Prometheus, have you:
promtool check config
promtool check rules
If your code touches Grafana, have you:
Checklist: