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 1uTiTN-008iA5-CJ for pgsql-hackers@arkaria.postgresql.org; Mon, 23 Jun 2025 14:48:37 +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 1uTiTL-003kaK-Fj for pgsql-hackers@arkaria.postgresql.org; Mon, 23 Jun 2025 14:48:36 +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.94.2) (envelope-from ) id 1uTiTL-003kaC-6C for pgsql-hackers@lists.postgresql.org; Mon, 23 Jun 2025 14:48:35 +0000 Received: from mout-p-201.mailbox.org ([80.241.56.171]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1uTiTK-003Yyg-04 for pgsql-hackers@lists.postgresql.org; Mon, 23 Jun 2025 14:48:34 +0000 Received: from smtp102.mailbox.org (smtp102.mailbox.org [10.196.197.102]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-201.mailbox.org (Postfix) with ESMTPS id 4bQrYV0KKBz9sx5; Mon, 23 Jun 2025 16:48:30 +0200 (CEST) Date: Mon, 23 Jun 2025 16:48:27 +0200 From: Christoph Berg To: Tomas Vondra Cc: pgsql-hackers@lists.postgresql.org Subject: Re: pgsql: Introduce pg_shmem_allocations_numa view Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Re: To Tomas Vondra > Why do we try to force the pages to be allocated at all? This is just > a monitoring function, it should not change the actual system state. One-time touching might also not be enough, what if the pages later get swapped out and the monitoring functions are called again? They will have to deal with these "not in memory" error conditions anyway. Christoph