Re: failed NUMA pages inquiry status: Operation not permitted

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: 2026-01-05 22:29:58
Message-ID: aVw7Zg9QngFiDOhr@msg.df7cb.de
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Re: Tomas Vondra
> I guess the only solution is to accept -2 as a possible value (unknown
> node). But that makes regression testing harder, because it means the
> output could change a lot ...

Or just not test that, or do something like

select numa_node = -2 or numa_node between 0 and 1000 from pg_shmem_allocations_numa;

Christoph

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Masahiko Sawada 2026-01-05 23:50:40 pgsql: pg_visibility: Fix incorrect buffer lock description in comment.
Previous Message Tom Lane 2026-01-05 22:27:18 Re: pgsql: Update to latest Snowball sources.

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2026-01-05 23:26:15 Re: Row pattern recognition
Previous Message Sami Imseih 2026-01-05 22:19:27 Re: Refactor query normalization into core query jumbling