Re: Draft for basic NUMA observability

Andres Freund <andres@anarazel.de>

From: Andres Freund <andres@anarazel.de>
To: Jakub Wartak <jakub.wartak@enterprisedb.com>
Cc: Tomas Vondra <tomas@vondra.me>, Bertrand Drouvot <bertranddrouvot.pg@gmail.com>, Alvaro Herrera <alvherre@alvh.no-ip.org>, Nazir Bilal Yavuz <byavuz81@gmail.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2025-04-07T17:24:20Z
Lists: pgsql-hackers
On 2025-04-04 19:07:12 +0200, Jakub Wartak wrote:
> They actually look good to me. We've discussed earlier dropping
> s/numa_//g for column names (after all views contain it already) so
> they are fine in this regard.
> There's also the question of consistency: (bufferid, page_num,
> node_id) -- maybe should just drop "_" and that's it?
> Well I would even possibly consider page_num -> ospagenumber, but that's ugly.

I'd go for os_page_num.



Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. doc: Correct pg_shmem_allocations_numa.size data type

  2. Add pg_buffercache_numa view with NUMA node info

  3. Add support for basic NUMA awareness

  4. Introduce pg_shmem_allocations_numa view