add postgres 17 upgrade steps to 2.39.0 upgrade notes #12585
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
|
No security concerns detected in this pull request. All finding details can be found in the DryRun Security Dashboard. |
valentijnscholten
changed the title
|
@paulOsinski wdyt? |
|
Docs look good to me - I'll defer to others to review the process itself as I don't have a way to test this today. |
mtesauro
requested changes
Jun 10, 2025
Maffooch
approved these changes
Jun 12, 2025
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.
A major version postgres update such as in 2.39.0 is non-trivial. This PR adds some notes to help users make the upgrade work.