feat: covering ranges for upgrades #1603
Merged
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
delgado3d
approved these changes
May 21, 2025
samrose
changed the title
damonrand
pushed a commit
to cepro/postgres
that referenced
this pull request
Jun 15, 2025
* feat: need to cover less than or equal to 15 * feat: handle range of 16 or greater for destination of upgrade * feat: use -ge approach for all instances of 16+ handling * chore: testing vers bump * chore: version bump for release
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.
In this PR we are expanding the coverage to pg major version equal to or less than 15, to cover pg 14 instances, for config adjustments that need to happen to upgrade postgres. Need to cover ranges for differences between 15 and lower, or 16 and higher (instead of specific version) for various operations.