Date: Thu, 16 Oct 2025 13:38:35 +0200
From: Christoph Berg <myon@debian.org>
To: Tomas Vondra <tomas.vondra@postgresql.org>,
	Jakub Wartak <jakub.wartak@enterprisedb.com>
Cc: pgsql-hackers@lists.postgresql.org
Subject: failed NUMA pages inquiry status: Operation not permitted
Message-ID: <aPDZOxjrmEo_1JRG@msg.df7cb.de>
References: <E1u1tr8-003BbN-2E@gemulon.postgresql.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="dtTMMoFAaZ2xgutH"
Content-Disposition: inline
In-Reply-To: <E1u1tr8-003BbN-2E@gemulon.postgresql.org>
Archived-At: 
 <https://www.postgresql.org/message-id/aPDZOxjrmEo_1JRG%40msg.df7cb.de>
Precedence: bulk


--dtTMMoFAaZ2xgutH
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

> src/test/regress/expected/numa.out       |  13 +++
> src/test/regress/expected/numa_1.out     |   5 +

numa_1.out is catching this error:

ERROR:  libnuma initialization failed or NUMA is not supported on this platform

This is what I'm getting when running PG18 in docker on Debian trixie
(libnuma 2.0.19).

However, on older distributions, the error is different:

postgres =# select * from pg_shmem_allocations_numa;
ERROR:  XX000: failed NUMA pages inquiry status: Operation not permitted
LOCATION:  pg_get_shmem_allocations_numa, shmem.c:691

This makes the numa regression tests fail in Docker on Debian bookworm
(libnuma 2.0.16) and older and all of the Ubuntu LTS releases.

The attached patch makes it accept these errors, but perhaps it would
be better to detect it in pg_numa_available().

Christoph

--dtTMMoFAaZ2xgutH
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
	filename="0001-numa-Catch-Operation-not-permitted-error.patch"