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 <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1v9Pal-0002bU-DZ
	for pgsql-hackers@arkaria.postgresql.org; Thu, 16 Oct 2025 15:08:34 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1v9Pak-00Dk1A-5u
	for pgsql-hackers@arkaria.postgresql.org; Thu, 16 Oct 2025 15:08:33 +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 <cb@df7cb.de>)
	id 1v9Paj-00Dk0b-Sk
	for pgsql-hackers@lists.postgresql.org; Thu, 16 Oct 2025 15:08:32 +0000
Received: from mout-p-202.mailbox.org ([2001:67c:2050:0:465::202])
	by magus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <cb@df7cb.de>)
	id 1v9Pag-002Xqn-39
	for pgsql-hackers@lists.postgresql.org;
	Thu, 16 Oct 2025 15:08:32 +0000
Received: from smtp202.mailbox.org (smtp202.mailbox.org
 [IPv6:2001:67c:2050:b231:465::202])
	(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-202.mailbox.org (Postfix) with ESMTPS id 4cnWYM62DKz9tPF;
	Thu, 16 Oct 2025 17:08:23 +0200 (CEST)
Authentication-Results: outgoing_mbo_mout;
	dkim=none;
	spf=pass (outgoing_mbo_mout: domain of cb@df7cb.de designates
 2001:67c:2050:b231:465::202 as permitted sender) smtp.mailfrom=cb@df7cb.de
Date: Thu, 16 Oct 2025 17:08:22 +0200
From: Christoph Berg <myon@debian.org>
To: Tomas Vondra <tomas@vondra.me>
Cc: Jakub Wartak <jakub.wartak@enterprisedb.com>,
	pgsql-hackers@lists.postgresql.org
Subject: Re: failed NUMA pages inquiry status: Operation not permitted
Message-ID: <aPEKZl_CUrjfdpTr@msg.df7cb.de>
References: <E1u1tr8-003BbN-2E@gemulon.postgresql.org>
 <aPDZOxjrmEo_1JRG@msg.df7cb.de>
 <7bbc582b-cc70-4a6f-bbf2-b5fd9b13a867@vondra.me>
 <aPEHINwaAxsQNAIP@msg.df7cb.de>
 <aPEJ7yH7ZJAF_MYW@msg.df7cb.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <aPEJ7yH7ZJAF_MYW@msg.df7cb.de>
X-Rspamd-Queue-Id: 4cnWYM62DKz9tPF
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Archived-At: 
 <https://www.postgresql.org/message-id/aPEKZl_CUrjfdpTr%40msg.df7cb.de>
Precedence: bulk

Re: To Tomas Vondra
> So maybe all that's needed is a get_mempolicy() call in
> pg_numa_available() ?

Or perhaps give up on pg_numa_available, and just have two _1.out and
_2.out that just contain the two different error messages, without
trying to catch the problem.

Christoph