pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Christoph Berg <myon@debian.org>
To: Tomas Vondra <tomas@vondra.me>
Cc: Jakub Wartak <jakub.wartak@enterprisedb.com>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: failed NUMA pages inquiry status: Operation not permitted
Date: Fri, 14 Nov 2025 13:52:59 +0100
Message-ID: <aRcmK8Bpi77yKbq1@msg.df7cb.de> (raw)
In-Reply-To: <a05ca971-a8ea-422f-85cd-b5edc46c5a9a@vondra.me>
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>

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...)

Christoph





view thread (29+ messages)  latest in thread

Message-ID: <aRcmK8Bpi77yKbq1@msg.df7cb.de>
Permalink:  ../aRcmK8Bpi77yKbq1@msg.df7cb.de/
Also on:    postgresql.org/message-id/aRcmK8Bpi77yKbq1@msg.df7cb.de

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: myon@debian.org, tomas@vondra.me, jakub.wartak@enterprisedb.com, pgsql-hackers@lists.postgresql.org
  Subject: Re: failed NUMA pages inquiry status: Operation not permitted
  In-Reply-To: <aRcmK8Bpi77yKbq1@msg.df7cb.de>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox