From: | Tomas Vondra <tomas(at)vondra(dot)me> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de>, Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com> |
Cc: | Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Draft for basic NUMA observability |
Date: | 2025-04-07 17:59:59 |
Message-ID: | 2525cef8-357e-4480-bd33-8fc2c8ba47a9@vondra.me |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 4/7/25 19:24, Andres Freund wrote:
> 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.
WFM. I've renamed "ospageid" to "os_page_num" in 0003, and I've also
renamed "node_id" to "numa_node" in 0002+0003, to make it clearer what
kind of node this is.
This reminds me whether it's fine to have "os_page_num" as int. Should
we make it bigint, perhaps?
Attached is v28, with the commit messages updated, added <warning> about
allocation of the memory, etc. I'll let the CI run the tests on it, and
then will push, unless someone has more comments.
regards
--
Tomas Vondra
Attachment | Content-Type | Size |
---|---|---|
v28-0001-Add-support-for-basic-NUMA-awareness.patch | text/x-patch | 22.1 KB |
v28-0002-Introduce-pg_shmem_allocations_numa-view.patch | text/x-patch | 18.9 KB |
v28-0003-Add-pg_buffercache_numa-view-with-NUMA-node-info.patch | text/x-patch | 22.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2025-04-07 18:00:43 | Re: Modern SHA2- based password hashes for pgcrypto |
Previous Message | Tom Lane | 2025-04-07 17:50:35 | Re: Modern SHA2- based password hashes for pgcrypto |