Repository navigation
Conversation
Postgres, its extensions, and everything loaded into the postgres process stay on nixpkgs fb7944c, glibc 2.40, through a new nixpkgs-pg17 input. After a glibc bump, Postgres warns that the collation version stored in each database differs from the running one. The main nixpkgs input moves to the nixos-26.05 channel so it can be updated on a schedule. All PG outputs keep their drvPath on x86_64-linux, aarch64-linux, and aarch64-darwin: psql_*, every extension, postgresql_*, postgres-env, site-env, extension catalogs, gatekeeper, and groonga. Also: - nix-darwin follows its nix-darwin-26.05 branch to match nixpkgs. - ext tests import QemuMachine, since 26.05 dropped test_driver Machine. - hstore_copy_binary writes inside the data dir, not a shared /tmp path that collides across unsandboxed darwin builds. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
brainrake
force-pushed
the
chore/pin-postgres-nixpkgs
branch
from
October 5, 2026 10:29
ac5986b to
384b696
Compare
PostgreSQL Extension Dependency Analysis: PR #2517
SummaryThe following extensions have dependencies that underwent MAJOR version updates:
Full Analysis ResultsPostgreSQL 15 Extension DependenciesExtension: http
Raw Dependency TreeExtension: hypopg
Raw Dependency TreeExtension: pg_cron
Raw Dependency TreeExtension: pg_graphql
Raw Dependency TreeExtension: pg_hashids
Raw Dependency TreeExtension: pg_jsonschema
Raw Dependency TreeExtension: pg_net
Raw Dependency TreeExtension: pg_partman
Raw Dependency TreeExtension: pg_repack
Raw Dependency TreeExtension: pg_stat_monitor
Raw Dependency TreeExtension: pg_tle
Raw Dependency TreeExtension: pgaudit
Raw Dependency TreeExtension: pgroonga
Raw Dependency TreeExtension: pgsodium
Raw Dependency TreeExtension: pgtap
Raw Dependency TreeExtension: plpgsql_check
Raw Dependency Tree |
PostgreSQL Package Dependency Analysis: PR #2517
SummaryThe following packages underwent 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 |
- Rename nixpkgs-pg17 to nixpkgs-pg, since it also builds pg15. - Import the main nixpkgs without overlays. Only nixpkgs-pg needs rust-overlay, cargo-pgrx, cgal, and the oldstable curl and v8. - Build site-env from the main nixpkgs, so supautils and gatekeeper pick up updates. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gatekeeper loads into postgres without an RPATH, like supautils, so site-env and postgres-env now share one build from the main nixpkgs. pg_regress and pg_isolation_regress are test clients. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Drop the nixpkgs-pg pin. Postgres and its extensions build from the nixos-26.05 nixpkgs too, which moves them to glibc 2.42. pg_net builds against the main curl instead of curl_8_6 from nixpkgs-oldstable. Versions before 0.20.4 need -DCURL_DISABLE_TYPECHECK, since newer curl headers break their multi.h include. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
brainrake
changed the title
glibc 2.42 re-versions cfgetospeed, so the bundled libncursesw needed GLIBC_2.42 and failed on Ubuntu 24.04. The bundle now ships an ncurses that resolves the GLIBC_2.17 symbol at runtime. Also fix the two nixos-26.05 deprecation warnings in groonga: a nested buildInputs list and the xxHash rename. Refs: MPG-1323 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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 (73 paths added, 73 paths removed, delta +0, disk usage +2.1MiB).x86_64-linux: Closure size: 74 -> 74 (74 paths added, 74 paths removed, delta +0, disk usage +1.8MiB). |
|
Found 1 test failure on Blacksmith runners: Failure
|
![Fix with [code]smith](https://pr-comments-assets.blacksmith.sh/codesmith/fix-with-codesmith-light.svg)
Collaborator
Author
|
Check current handling of collation version mismatch and proceed accordingly re. glibc 2.42 |
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
1 participant
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.
Why
What
nixpkgsmoves from nixos-unstablefb7944cto thenixos-26.05channel for everything, Postgres and every extension included. glibc goes from 2.40-66 to 2.42-84.nix-darwinfollowsnix-darwin-26.05to match the nixpkgs release.curl_8_6fromnixpkgs-oldstable. Versions before 0.20.4 build with-DCURL_DISABLE_TYPECHECK.nix/ext/tests/lib.pyimportsQemuMachine. The 26.05 test driver droppedtest_driver.machine.Machine.hstore_copy_binarywrites its file inside the data directory. The fixed/tmppath collided across unsandboxed darwin builds that run as different_nixbldusers.After deploy, libc-provider databases warn that their stored collation version differs from glibc 2.42 until they run
ALTER DATABASE ... REFRESH COLLATION VERSION. Sort order doesn't change. The dependency changelog review is in a comment below.Verification
MPG-1323