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 1vVpO2-008mYQ-0d for pgsql-hackers@arkaria.postgresql.org; Wed, 17 Dec 2025 11:08:07 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vVpO0-00CGvu-2s for pgsql-hackers@arkaria.postgresql.org; Wed, 17 Dec 2025 11:08:05 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vVpO0-00CGvm-1R for pgsql-hackers@lists.postgresql.org; Wed, 17 Dec 2025 11:08:05 +0000 Received: from relay7-d.mail.gandi.net ([2001:4b98:dc4:8::227]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vVpNy-0018TP-34 for pgsql-hackers@lists.postgresql.org; Wed, 17 Dec 2025 11:08:04 +0000 Received: by mail.gandi.net (Postfix) with ESMTPSA id 24B514317E; Wed, 17 Dec 2025 11:07:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vondra.me; s=gm1; t=1765969674; 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=HS3eYOTXyFQo5CRRsgedTNyNzoCiw/PYSFPNlhpfisU=; b=HTd+GYnsDsynyYHswRnIoJJu/haznDAVlDAboRUbsWN/nfR21ijDKfoMq2mjUreqCMIq8H +PIfQyO9bIP4fKKuce653bAszP4zzTKz5QYezbjYO7IQwOeIBmEqCN7jhKcvc0BUfUMJSK KVFXJO/QoY5dt60RUKtCYRZxIn/eaU27nBAqrVG2rysWiTS4e9f8yyzw1+dJ7uY1AyDSX9 qVAHWj2sBKkQqkiton9R8UiJu+HX4xFlRqOUpODPD2T1Cv5iVt9dj8xyyQgoa6defqE29/ XtKeeDhz16NbEhQi1kXNNafU8siDfsXiu7n67GjyW3RJG9E5udg1AhFq0Xx03w== Message-ID: Date: Wed, 17 Dec 2025 12:07:53 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: failed NUMA pages inquiry status: Operation not permitted To: Christoph Berg Cc: Jakub Wartak , pgsql-hackers@lists.postgresql.org References: <54329add-59b6-4c08-96f0-a025a7804174@vondra.me> <4ff9578d-1de2-45c1-98c4-29caf99334ff@vondra.me> <183fe9ab-6010-4cca-b648-1deca332ce2a@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 X-GND-State: clean X-GND-Score: -100 X-GND-Cause: gggruggvucftvghtrhhoucdtuddrgeefgedrtddtgdegvdegtdcutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfitefpfffkpdcuggftfghnshhusghstghrihgsvgenuceurghilhhouhhtmecufedtudenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhepkfffgggfuffvvehfhfgjtgfgsehtjeertddtvdejnecuhfhrohhmpefvohhmrghsucggohhnughrrgcuoehtohhmrghssehvohhnughrrgdrmhgvqeenucggtffrrghtthgvrhhnpeeludegieekgfelhffgffeuvdelteetveeghfdvieekfeduudduvdfhvedufefhveenucfkphepkeeirdegledrvdeftddrvddtieenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepihhnvghtpeekiedrgeelrddvfedtrddvtdeipdhhvghloheplgdutddrudefjedrtddrvdgnpdhmrghilhhfrhhomhepthhomhgrshesvhhonhgurhgrrdhmvgdpqhhiugepvdegueehudegfedujefgpdhmohguvgepshhmthhpohhuthdpnhgspghrtghpthhtohepfedprhgtphhtthhopehmhihonhesuggvsghirghnrdhorhhgpdhrtghpthhtohepjhgrkhhusgdrfigrrhhtrghksegvnhhtvghrphhrihhsvggusgdrtghomhdprhgtphhtthhopehpghhsqhhlqdhhrggtkhgvrhhssehlihhsthhsrdhpohhsthhgrhgvshhqlhdrohhrgh List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 12/16/25 18:54, Christoph Berg wrote: > Re: Tomas Vondra >> 1) right after opening a connection, I get this >> >> test=# select numa_node, count(*) from pg_buffercache_numa group by 1; >> numa_node | count >> -----------+------- >> 0 | 290 >> -2 | 32478 > > Does that mean that the "touch all pages" logic is missing in some > code paths? > I did check and AFAICS we are touching the pages in pg_buffercache_numa. To make it even more confusing, I can no longer reproduce the behavior I reported yesterday. It just consistently reports "0" and I have no idea why it changed :-( I did restart since yesterday, so maybe that changed something. > But even with that, it seems to be able to degenerate again and > accepting -2 in the regression tests would be required to make it > stable. > No opinion yet. Either the -2 can happen occasionally, and then we'd need to adjust the regression tests. Or maybe it's some thinko, and then it'd be good to figure out why it's happening. I find it interesting it does not seem to fail on the buildfarm. Or at least I'm not aware of such failures. Even a rare failure should show itself on the buildfarm a couple times, so how come it didn't? regards -- Tomas Vondra