Message-ID: <54329add-59b6-4c08-96f0-a025a7804174@vondra.me>
Date: Thu, 20 Nov 2025 13:53:48 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: failed NUMA pages inquiry status: Operation not permitted
To: Christoph Berg <myon@debian.org>
Cc: Jakub Wartak <jakub.wartak@enterprisedb.com>,
 pgsql-hackers@lists.postgresql.org
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>
 <aPENGAkcrLyB_NLC@msg.df7cb.de>
 <a05ca971-a8ea-422f-85cd-b5edc46c5a9a@vondra.me>
 <aRcmK8Bpi77yKbq1@msg.df7cb.de>
Content-Language: en-US
From: Tomas Vondra <tomas@vondra.me>
In-Reply-To: <aRcmK8Bpi77yKbq1@msg.df7cb.de>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/54329add-59b6-4c08-96f0-a025a7804174%40vondra.me>
Precedence: bulk

On 11/14/25 13:52, Christoph Berg wrote:
> Re: Tomas Vondra
>> So I'm leaning to adjust pg_numa_init() to also check EPERM, per the
>> attached patch. It still calls numa_available(), so that we don't
>> silently miss future libnuma changes.
>>
>> Can you check this makes it work inside the docker container?
> 
> Yes your patch works. (Sorry I meant to test earlier, but RL...)
> 

Thanks. I've pushed the fix (and backpatched to 18).


regards

-- 
Tomas Vondra