talexander/nixpkgs
1
0
Fork 0
Code Issues Pull Requests Releases Activity

postgresql_18: turn off NUMA support in 18beta2 as well

Browse Source 
Follows up on #426118

Still produces a broken test:

    diff -U3 /build/source/src/test/regress/expected/numa.out /build/source/src/test/regress/results/numa.out
    --- /build/source/src/test/regress/expected/numa.out	1970-01-01 00:00:01.000000000 +0000
    +++ /build/source/src/test/regress/results/numa.out	2025-07-19 08:44:02.793368816 +0000
    @@ -6,8 +6,4 @@
     -- switch to superuser
     \c -
     SELECT COUNT(*) >= 0 AS ok FROM pg_shmem_allocations_numa;
    - ok
    -----
    - t
    -(1 row)
    -
    +ERROR:  invalid NUMA node id outside of allowed range [0, 0]: 1
This commit is contained in:
Maximilian Bosch 2025-07-19 11:27:02 +02:00
parent 4aef182424
commit cf0661c6f3
No known key found for this signature in database
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
pkgs/servers/sql/postgresql/generic.nix
View File

@ -102,11 +102,11 @@ let
numaSupport ?
lib.versionAtLeast version "18"
&& lib.meta.availableOn stdenv.hostPlatform numactl
# NUMA can fail in 18beta1 on some hardware with:
# NUMA can fail in 18beta2 on some hardware with:
# ERROR: invalid NUMA node id outside of allowed range [0, 0]: 1
# https://github.com/NixOS/nixpkgs/pull/411958#issuecomment-3031680123
# https://www.postgresql.org/message-id/flat/E1u1tr8-003BbN-2E%40gemulon.postgresql.org
&& version != "18beta1",
&& version != "18beta2",
numactl,
# PAM