Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1v9PcF-0002zg-AH for pgsql-hackers@arkaria.postgresql.org; Thu, 16 Oct 2025 15:10:06 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1v9PcE-00DmUl-8L for pgsql-hackers@arkaria.postgresql.org; Thu, 16 Oct 2025 15:10:05 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1v9PcD-00DmTi-VQ for pgsql-hackers@lists.postgresql.org; Thu, 16 Oct 2025 15:10:04 +0000 Received: from relay5-d.mail.gandi.net ([217.70.183.197]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1v9PcA-002XsJ-1w for pgsql-hackers@lists.postgresql.org; Thu, 16 Oct 2025 15:10:04 +0000 Received: by mail.gandi.net (Postfix) with ESMTPSA id 3B0E243A75; Thu, 16 Oct 2025 15:10:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vondra.me; s=gm1; t=1760627400; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=WmmmbI6VhsN9efn8ZDmV1Wpetrx/9WJK7MeUdvcGyK4=; b=Yr3n/5ooBTgrLGham/Es+I7Q9WC7i19YKAtUYgxneG3kyQVY+u060I/PTjons7VVb4mfyG aPZjmOGxgp02SIeN/EfKDXbJPT8AHz1IogI+g2u9cW60a4jrmyuGBJf7ehgHKCMSi0DrI2 pPUiFApg/b0t5Y5cSYQ6vxfNhTwonZ3gpEkIfB9YV99LmfGNNaL2eKX7WfxS6StDCGwVm0 /rn75VWFSJgZGvwZlJ6gk+ey6XNgJ8gH3KBAsE8S5+lHDMLt1hf4ovK1dnQGzHrreiV6H6 9PDMdNIeJPrUMQjnhhIy3hfQl+czuA0jILE965x0gDgaYVNa5FKPn7uQaTP8Kg== Message-ID: <20d4c8a3-a402-4426-a912-8261e8923adf@vondra.me> Date: Thu, 16 Oct 2025 17:09:59 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: failed NUMA pages inquiry status: Operation not permitted To: Christoph Berg Cc: Tomas Vondra , Jakub Wartak , pgsql-hackers@lists.postgresql.org References: <7bbc582b-cc70-4a6f-bbf2-b5fd9b13a867@vondra.me> Content-Language: en-US From: Tomas Vondra In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-GND-Sasl: tomas@vondra.me List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 10/16/25 16:54, Christoph Berg wrote: > 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 > Hmmm. Those seem like relatively recent kernels. >> 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. > move_page() manpage mentions PTRACE_MODE_READ_REALCREDS (man ptrace) so maybe that's it. -- Tomas Vondra