Date: Thu, 16 Oct 2025 16:54:24 +0200
From: Christoph Berg <myon@debian.org>
To: Tomas Vondra <tomas@vondra.me>
Cc: Tomas Vondra <tomas.vondra@postgresql.org>,
	Jakub Wartak <jakub.wartak@enterprisedb.com>,
	pgsql-hackers@lists.postgresql.org
Subject: Re: failed NUMA pages inquiry status: Operation not permitted
Message-ID: <aPEHINwaAxsQNAIP@msg.df7cb.de>
References: <E1u1tr8-003BbN-2E@gemulon.postgresql.org>
 <aPDZOxjrmEo_1JRG@msg.df7cb.de>
 <7bbc582b-cc70-4a6f-bbf2-b5fd9b13a867@vondra.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <7bbc582b-cc70-4a6f-bbf2-b5fd9b13a867@vondra.me>
Archived-At: 
 <https://www.postgresql.org/message-id/aPEHINwaAxsQNAIP%40msg.df7cb.de>
Precedence: bulk

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