update docs to PostgreSQL 16 #11215
Open
update docs to PostgreSQL 16 #11215
Conversation
This file contains 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
pdurbin
reviewed
Feb 4, 2025
| @@ -97,21 +97,21 @@ Also note that Payara may utilize more than the default number of file descripto | |||
| PostgreSQL | |||
| ---------- | |||
|
|
|||
There was a problem hiding this comment.
I'll just put his up here at the top. Please add a release note snippet.
Should it ask that developers switch to 16 or higher? 🤔
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.
What this PR does / why we need it:
PostgreSQL EOLs in November 2025
Which issue(s) this PR closes:
Special notes for your reviewer:
I tried to avoid RHEL7/9 yum/dnf changes for the sake of granularity, but line 109 was unavoidable.
Suggestions on how to test this:
Follow installation routine.
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
no
Is there a release notes update needed for this change?:
Not particularly, as this is targeted at totally new installations without experience administering PostgreSQL.
Additional documentation:
none