Re: Adding basic NUMA awareness - Preliminary feedback and outline for an extensible approach
Cédric Villemain <cedric.villemain@data-bene.io>
From: Cédric Villemain <cedric.villemain@data-bene.io>
To: Tomas Vondra <tomas@vondra.me>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-07-07T14:51:00Z
Lists: pgsql-hackers
>> * Others might use it to integrate PostgreSQL's own resources (e.g., >> "areas" of shared buffers) into policies. >> >> Hope this perspective is helpful. > > Can you explain how you want to manage this by an extension defined at > the SQL level, when most of this stuff has to be done when setting up > shared memory, which is waaaay before we have any access to catalogs? I should have said module instead, I didn't follow carefully but at some point there were discussion about shared buffers resized "on-line". Anyway, it was just to give some few examples, maybe this one is to be considered later (I'm focused on cgroup/psi, and precisely reassigning PIDs as needed). -- Cédric Villemain +33 6 20 30 22 52 https://www.Data-Bene.io PostgreSQL Support, Expertise, Training, R&D
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Sort guc_parameters.dat alphabetically by name
- fce7c73fba4e 19 (unreleased) cited