Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add initial changes for PG16 compatibility and pgMonitor 4.10.0 bump #3737

Merged
merged 2 commits into from
Oct 3, 2023

Conversation

dsessler7
Copy link
Contributor

Checklist:

  • Have you added an explanation of what your changes do and why you'd like them to be included?
  • Have you updated or added documentation for the change, as applicable?
  • Have you tested your changes on all related environments with successful results, as applicable?
    • Have you added automated tests?

Type of Changes:

  • New feature
  • Bug fix
  • Documentation
  • Testing enhancement
  • Other

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)?

  • Breaking change (fix or feature that would cause existing functionality to 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:

@dsessler7 dsessler7 force-pushed the pg_16_compatibility branch from 1d203eb to 2da0d31 Compare October 3, 2023 18:29
@dsessler7 dsessler7 merged commit 3a96ba7 into CrunchyData:master Oct 3, 2023
13 of 14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants