add initial changes for PG16 compatibility and pgMonitor 4.10.0 bump #3737
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.
Checklist:
Type of Changes:
What is the current behavior (link to any open issues here)?
The max postgres version that
postgres-operator
is currently compatible with is 15. Also, it is set to use pgMonitor 4.9.0.What is the new behavior (if this is a feature change)?
This change will change the max postgres version that
postgres-operator
can use to 16. Will also be setup to pgMonitor 4.10.0.Other Information: