From: | Christoph Berg <myon(at)debian(dot)org> |
---|---|
To: | Tomas Vondra <tomas(at)vondra(dot)me> |
Cc: | Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: failed NUMA pages inquiry status: Operation not permitted |
Date: | 2025-10-16 15:06:23 |
Message-ID: | aPEJ7yH7ZJAF_MYW@msg.df7cb.de |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Re: To Tomas Vondra
> It's the very same kernel, just different docker containers on the
> same system. I did not investigate yet where the problem is coming
> from, different libnuma versions seemed like the best bet.
numactl shows the problem already:
Host system:
$ numactl --show
policy: default
preferred node: current
physcpubind: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
cpubind: 0
nodebind: 0
membind: 0
preferred:
debian:trixie-slim container:
$ numactl --show
physcpubind: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
No NUMA support available on this system.
debian:bookworm-slim container:
$ numactl --show
get_mempolicy: Operation not permitted
get_mempolicy: Operation not permitted
get_mempolicy: Operation not permitted
get_mempolicy: Operation not permitted
policy: default
preferred node: current
physcpubind: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
cpubind: 0
nodebind: 0
membind: 0
preferred:
Running with sudo does not change the result.
So maybe all that's needed is a get_mempolicy() call in
pg_numa_available() ?
Christoph
From | Date | Subject | |
---|---|---|---|
Next Message | Christoph Berg | 2025-10-16 15:08:22 | Re: failed NUMA pages inquiry status: Operation not permitted |
Previous Message | Christoph Berg | 2025-10-16 14:54:24 | Re: failed NUMA pages inquiry status: Operation not permitted |
From | Date | Subject | |
---|---|---|---|
Next Message | Christoph Berg | 2025-10-16 15:08:22 | Re: failed NUMA pages inquiry status: Operation not permitted |
Previous Message | Aya Iwata (Fujitsu) | 2025-10-16 15:04:09 | RE: [PROPOSAL] Termination of Background Workers for ALTER/DROP DATABASE |