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: 2025-12-16 17:54:46
Message-ID: aUGc5qh977Y4r_jP@msg.df7cb.de
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Re: Tomas Vondra
> 1) right after opening a connection, I get this
>
> test=# select numa_node, count(*) from pg_buffercache_numa group by 1;
> numa_node | count
> -----------+-------
> 0 | 290
> -2 | 32478

Does that mean that the "touch all pages" logic is missing in some
code paths?

But even with that, it seems to be able to degenerate again and
accepting -2 in the regression tests would be required to make it
stable.

Christoph

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Noah Misch 2025-12-16 18:05:22 pgsql: Update .abi-compliance-history for CacheInvalidateHeapTupleInpla
Previous Message Robert Haas 2025-12-16 17:31:47 pgsql: Switch memory contexts in ReinitializeParallelDSM.

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2025-12-16 18:07:34 Re: [PATCH] Fix ARM64/MSVC atomic memory ordering issues on Win11 by adding explicit DMB ?barriers
Previous Message Andres Freund 2025-12-16 17:45:17 Re: Replace is_publishable_class() with relispublishable column in pg_class