| From: | Christoph Berg <myon(at)debian(dot)org> |
|---|---|
| To: | Tomas Vondra <tomas(at)vondra(dot)me> |
| 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-14 12:52:59 |
| Message-ID: | aRcmK8Bpi77yKbq1@msg.df7cb.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2025-11-14 13:42:42 | pgsql: pgbench: Fix assertion failure with multiple \syncpipeline in pi |
| Previous Message | Álvaro Herrera | 2025-11-14 11:01:10 | pgsql: Doc: add IDs to copy.sgml's <varlistentry> and <refsect1> |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2025-11-14 12:57:28 | Re: [Patch] Mention md5 is deprecated in postgresql.conf.sample |
| Previous Message | Michael Banck | 2025-11-14 12:15:43 | Re: [Patch] Mention md5 is deprecated in postgresql.conf.sample |