Re: failed NUMA pages inquiry status: Operation not permitted
| От | Tomas Vondra |
|---|---|
| Тема | Re: failed NUMA pages inquiry status: Operation not permitted |
| Дата | |
| Msg-id | 7bbc582b-cc70-4a6f-bbf2-b5fd9b13a867@vondra.me обсуждение исходный текст |
| Ответ на | failed NUMA pages inquiry status: Operation not permitted (Christoph Berg <myon@debian.org>) |
| Ответы |
Re: failed NUMA pages inquiry status: Operation not permitted
|
| Список | pgsql-hackers |
On 10/16/25 13:38, Christoph Berg wrote: >> src/test/regress/expected/numa.out | 13 +++ >> src/test/regress/expected/numa_1.out | 5 + > > numa_1.out is catching this error: > > ERROR: libnuma initialization failed or NUMA is not supported on this platform > > This is what I'm getting when running PG18 in docker on Debian trixie > (libnuma 2.0.19). > > However, on older distributions, the error is different: > > postgres =# select * from pg_shmem_allocations_numa; > ERROR: XX000: failed NUMA pages inquiry status: Operation not permitted > LOCATION: pg_get_shmem_allocations_numa, shmem.c:691 > > This makes the numa regression tests fail in Docker on Debian bookworm > (libnuma 2.0.16) and older and all of the Ubuntu LTS releases. > It's probably more about the kernel version. What kernels are used by these systems? > The attached patch makes it accept these errors, but perhaps it would > be better to detect it in pg_numa_available(). > Not sure how would that work. It seems this is some sort of permission check in numa_move_pages, that's not what pg_numa_available does. Also, it may depending on the page queried (e.g. whether it's exclusive or shared by multiple processes). thanks -- Tomas Vondra
В списке pgsql-hackers по дате отправления: