Conversation
PostgreSQL Extension Dependency Analysis: PR #2155
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 Tree |
PostgreSQL Package Dependency Analysis: PR #2155
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 |
utkarash2991
marked this pull request as ready for review
May 27, 2026 18:57
utkarash2991
marked this pull request as draft
May 27, 2026 19:16
utkarash2991
marked this pull request as ready for review
May 27, 2026 19:23
utkarash2991
force-pushed
the
pg-17-10-update
branch
2 times, most recently
from
May 29, 2026 21:29
c824b2f to
366159a
Compare
utkarash2991
force-pushed
the
pg-17-10-update
branch
from
June 1, 2026 16:36
0530b1d to
6c6c99f
Compare
This was referenced Jul 17, 2026
|
supabase, doesnt wanna release this or it prioritize paid user? |
|
@SpaceM88 hey, I'm waiting with you 👯 |
Collaborator
Author
|
We're returning to this soon. |
|
hey @samrose , now it's postgres 17.11 and 18.6 . it's almost a year and next will be postgres 19.0. are you going to support the postgres 17.11, 18.6 and 19.0? |
mmlb
changed the title
mmlb
marked this pull request as draft
August 21, 2026 23:53
This comment has been minimized.
This comment has been minimized.
utkarash2991
marked this pull request as ready for review
August 24, 2026 16:46
utkarash2991
force-pushed
the
pg-17-10-update
branch
from
August 24, 2026 16:53
726df40 to
740d287
Compare
mmlb
reviewed
Aug 24, 2026
mmlb
reviewed
Aug 24, 2026
Collaborator
We already support multiple PG versions in the repo, 15, 17 and 17+orioledb already exist. Most of the delay for 17/18 have been testing involved and man power. We've gotten some more folk on board so have been able to make progress recently. I'm not sure we'll do 18 and might just skip over to 19 tbh. |
|
Cool! I've been waiting for Postgres 18 support since last year :D Hopefully PG 19 support lands sooner. |
mmlb
force-pushed
the
pg-17-10-update
branch
2 times, most recently
from
September 16, 2026 18:54
c555c08 to
d764f5e
Compare
mmlb
force-pushed
the
pg-17-10-update
branch
2 times, most recently
from
September 23, 2026 22:02
e2d8332 to
b0f0c52
Compare
Collaborator
|
I'm going to bring #2166 and #2195's contents in via this PR. Bringing them in before the upgrade so I can verify in CI that they reproduce the issues and thus can be confident the upgrades do in fact fix them and regression tests will catch if they come back. This first run is going to fail once we hit the hstore regression test due to postgres crashing and not being restarted, next commit skips hstore so the rest of the tests will be able to fail as expected. Upgrade will show tests now pass w/o any changes to them (hstore test will be brought back in to the list). |
Collaborator
|
ok hit the hstore failures, so just pushed commit to filter it out from tests to run. |
mmlb
force-pushed
the
pg-17-10-update
branch
from
September 24, 2026 15:15
31d5083 to
5419f89
Compare
mmlb
removed this pull request from stack #2415
September 24, 2026 15:33
mmlb
force-pushed
the
pg-17-10-update
branch
5 times, most recently
from
September 25, 2026 22:45
ba55366 to
07c7551
Compare
Sorted runtimeInputs and indented code in `if`s because they annoyed me. I moved the check for postgresql.conf to right after it was first created because it doesn't really make much sense to do it later than necessary.
mmlb
force-pushed
the
pg-17-10-update
branch
from
September 28, 2026 16:31
07c7551 to
98a7877
Compare
mmlb
marked this pull request as ready for review
September 28, 2026 16:32
mmlb
force-pushed
the
pg-17-10-update
branch
2 times, most recently
from
September 28, 2026 19:38
0d9f768 to
d06f87d
Compare
pg_regress suite under nix/tests/sql pinning this release's CVE and behavior-change fixes. - btree_gist_nan (fix NaN handling for float4 & float8) - create_statistics_priv (CVE-2025-12817) - hstore_copy_binary (CVE-2026-6472) - intarray_ltree_query (CVE-2026-6473) - ltree_label_overflow (fix integer overflow in comparisons) - multirange_create_priv (CVE-2026-6472) - operator_breaking_change (CVE-2026-2004) - output_plugin_libraries (CVE-2026-6471) - pgcrypto_cipher_matrix (CVE-2026-14663) All skipped on orioledb-17 because its based on 17.9. CLI variant skips output_plugin_libraries and btree_gist_nan since logical-decoding infra / btree_gist not primed there. Refs: MPG-140, MPG-164 - merge_serialization (must raise serialization failure (40001) under REPEATABLE READ when its target row was updated+committed concurrently) Ref: MPG-163 Assisted-By: Claude Opus 4.8 <noreply@anthropic.com>
This crashes postgres and we don't have automatic restarts in these tests (as seen in last commit's ci run).
mmlb
force-pushed
the
pg-17-10-update
branch
from
September 28, 2026 22:02
d06f87d to
09058b1
Compare
PG 15.19/17.11 introduces output_plugin_libraries (CVE-2026-6471) defaulting to pgoutput and test_decoding only, which breaks wal2json slots (Realtime, CI wal2json tests). Allow wal2json in the shared config.
Was only here as an example test and did nothing, now that we have *real* test this can be dropped.
mmlb
force-pushed
the
pg-17-10-update
branch
from
September 28, 2026 22:05
09058b1 to
c84e81f
Compare
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
5 participants
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?
Bump Postgres 15.14 → 15.19 and 17.6 → 17.11 (upstream security releases of 2026-08-13), absorbing five upstream minors per major — 44 CVEs total, including CVE-2026-19385, CVE-2026-16239, CVE-2026-14669 (all CVSS 8.8).
Breaking change analysis
Full analysis in MPG-140