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.96) (envelope-from ) id 1vUTXV-00CbF3-01 for pgsql-hackers@arkaria.postgresql.org; Sat, 13 Dec 2025 17:36:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vUTXS-00BHPz-2z for pgsql-hackers@arkaria.postgresql.org; Sat, 13 Dec 2025 17:36:15 +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.96) (envelope-from ) id 1vUTXS-00BHPr-22 for pgsql-hackers@lists.postgresql.org; Sat, 13 Dec 2025 17:36:15 +0000 Received: from goedel.df7cb.de ([49.13.90.212]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vUTXN-000YzB-2u for pgsql-hackers@lists.postgresql.org; Sat, 13 Dec 2025 17:36:15 +0000 Received: from msg.df7cb.de (unknown [IPv6:2a02:908:1472:9340:f0ad:fc6e:9c86:f1dc]) by goedel.df7cb.de (Postfix) with ESMTPSA id 088D046AA4; Sat, 13 Dec 2025 17:36:07 +0000 (UTC) Date: Sat, 13 Dec 2025 18:36:07 +0100 From: Christoph Berg To: Tomas Vondra Cc: Jakub Wartak , pgsql-hackers@lists.postgresql.org Subject: Re: failed NUMA pages inquiry status: Operation not permitted Message-ID: References: <7bbc582b-cc70-4a6f-bbf2-b5fd9b13a867@vondra.me> <54329add-59b6-4c08-96f0-a025a7804174@vondra.me> <4ff9578d-1de2-45c1-98c4-29caf99334ff@vondra.me> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4ff9578d-1de2-45c1-98c4-29caf99334ff@vondra.me> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Re: Tomas Vondra > Hmmm, strange. -2 is ENOENT, which should mean this: > > -ENOENT > The page is not present. > > But what does "not present" mean in this context? And why would that be > only intermittent? Presumably this is still running in Docker, so maybe > it's another weird consequence of that? Sorry I forgot to mention that this is now in the normal apt.pg.o build environment (chroots without any funky permission restrictions). I have not tried Docker yet. I think it was not happening before the backport of the Docker fix. But I have no idea why this should have broken anything, and why it would only happen like 3% of the time. Christoph