From: Christoph Berg <myon@debian.org>
To: Tomas Vondra <tomas@vondra.me>
Cc: Tomas Vondra <tomas.vondra@postgresql.org>
Cc: Jakub Wartak <jakub.wartak@enterprisedb.com>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: failed NUMA pages inquiry status: Operation not permitted
Date: Thu, 16 Oct 2025 16:54:24 +0200
Message-ID: <aPEHINwaAxsQNAIP@msg.df7cb.de> (raw)
In-Reply-To: <7bbc582b-cc70-4a6f-bbf2-b5fd9b13a867@vondra.me>
References: <E1u1tr8-003BbN-2E@gemulon.postgresql.org>
<aPDZOxjrmEo_1JRG@msg.df7cb.de>
<7bbc582b-cc70-4a6f-bbf2-b5fd9b13a867@vondra.me>
Re: Tomas Vondra
> It's probably more about the kernel version. What kernels are used by
> these systems?
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.
Same (differing) results on both these systems:
Linux turing 6.16.7+deb14-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.16.7-1 (2025-09-11) x86_64 GNU/Linux
Linux jenkins 6.1.0-39-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.148-1 (2025-08-26) x86_64 GNU/Linux
> 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).
It's probably the lack of some process capability in that environment.
Maybe there is a way to query that, but I don't know much about that
yet.
Christoph
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: myon@debian.org, tomas@vondra.me, tomas.vondra@postgresql.org, jakub.wartak@enterprisedb.com, pgsql-hackers@lists.postgresql.org
Subject: Re: failed NUMA pages inquiry status: Operation not permitted
In-Reply-To: <aPEHINwaAxsQNAIP@msg.df7cb.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox