Re: failed NUMA pages inquiry status: Operation not permitted

From: Tomas Vondra <tomas(at)vondra(dot)me>
To: Christoph Berg <myon(at)debian(dot)org>
Cc: Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: failed NUMA pages inquiry status: Operation not permitted
Date: 2025-11-20 12:53:48
Message-ID: 54329add-59b6-4c08-96f0-a025a7804174@vondra.me
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

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

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Daniel Gustafsson 2025-11-20 13:51:39 pgsql: doc: Document how to run a subset of regress tests
Previous Message Tomas Vondra 2025-11-20 12:50:24 pgsql: Handle EPERM in pg_numa_init

Browse pgsql-hackers by date

  From Date Subject
Next Message Nazir Bilal Yavuz 2025-11-20 12:55:43 Re: Speed up COPY FROM text/CSV parsing using SIMD
Previous Message Xuneng Zhou 2025-11-20 12:43:06 Re: Implement waiting for wal lsn replay: reloaded