Repository navigation
PG 17.12 & 15.20 - #2648
Draft
mmlb wants to merge 2 commits into
Draft
PG 17.12 & 15.20#2648mmlb wants to merge 2 commits into
mmlb wants to merge 2 commits into
Conversation
mmlb
changed the title
Relevant to us/customers that we should ensure correct behavior.
mmlb
force-pushed
the
mannymendez/mpg-1558-update-postgres-to-1520-and-1712
branch
from
November 12, 2026 20:05
316c7eb to
3a68eea
Compare
Package version diff: none () |
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
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 kind of change does this PR introduce?
Feature
What is the current behavior?
Latest version of PG we run is old and has many bugs and CVEs,
15.19&17.11.What is the new behavior?
Latest version of PG is shiny and definitely has no bugs nor CVEs,
15.20&17.20.