Repository navigation
PG 17.12 & 15.20 - #2648
Merged
mmlb merged 4 commits intoNov 13, 2026
Merged
PG 17.12 & 15.20#2648
Conversation
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 diffCompares built package versions in legacyPackages between this PR and the tip of the base branch, per system. aarch64-linux: Closure size: 73 -> 73 (2 paths added, 2 paths removed, delta +0, disk usage +0B).x86_64-linux: Closure size: 74 -> 74 (2 paths added, 2 paths removed, delta +0, disk usage +0B). |
This comment has been minimized.
This comment has been minimized.
We already have this info in nix/config.nix and we can grab it from there so lets just do that.
mmlb
force-pushed
the
mannymendez/mpg-1558-update-postgres-to-1520-and-1712
branch
from
November 13, 2026 15:00
3a68eea to
5682790
Compare
PostgreSQL Extension Dependency Analysis: PR #2648
SummaryNo extensions had dependencies with MAJOR version updates. Full Analysis ResultsPostgreSQL 15 Extension DependenciesExtension: pg_cron
Raw Dependency TreeExtension: pg_repack
Raw Dependency TreeExtension: postgis
Raw Dependency TreeExtension: wrappers
Raw Dependency TreePostgreSQL 17 Extension DependenciesExtension: pg_cron
Raw Dependency TreeExtension: pg_repack
Raw Dependency TreeExtension: postgis
Raw Dependency TreeExtension: wrappers
Raw Dependency TreeOrioleDB 17 Extension Dependencies |
PostgreSQL Package Dependency Analysis: PR #2648
SummaryNo packages had MAJOR version updates. Full Analysis ResultsPostgreSQL 15 Dependency ChangesExtracting PostgreSQL 15 dependencies...
Runtime Closure Size
Raw Dependency ClosurePostgreSQL 17 Dependency ChangesExtracting PostgreSQL 17 dependencies...
Runtime Closure Size
Raw Dependency Closure |
brainrake
reviewed
Nov 13, 2026
mmlb
force-pushed
the
mannymendez/mpg-1558-update-postgres-to-1520-and-1712
branch
3 times, most recently
from
November 13, 2026 18:51
d69d4f9 to
9c5df4c
Compare
Relevant to us/customers that we should ensure correct behavior.
mmlb
force-pushed
the
mannymendez/mpg-1558-update-postgres-to-1520-and-1712
branch
2 times, most recently
from
November 13, 2026 19:18
0dea074 to
130256a
Compare
mmlb
marked this pull request as ready for review
November 13, 2026 19:18
brainrake
approved these changes
Nov 13, 2026
brainrake
left a comment
Collaborator
There was a problem hiding this comment.
Maybe update README.md:183-184: postgresql-15.19 and postgresql-17.11.
Member
17.20👀 |
Collaborator
Author
|
gah my fingers keep doing that |
mmlb
force-pushed
the
mannymendez/mpg-1558-update-postgres-to-1520-and-1712
branch
from
November 13, 2026 20:39
130256a to
2bea3e5
Compare
mmlb
enabled auto-merge
November 13, 2026 20:40
mmlb
deleted the
mannymendez/mpg-1558-update-postgres-to-1520-and-1712
branch
November 13, 2026 20:58
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,
17.11&15.19.What is the new behavior?
Latest version of PG is shiny and definitely has no bugs nor CVEs,
17.12&15.20.