public inbox for [email protected]  

help / color / mirror / Atom feed

From: Cédric Villemain <[email protected]>
To: Tomas Vondra <[email protected]>
To: PostgreSQL Hackers <[email protected]>
Subject: Re: Adding basic NUMA awareness - Preliminary feedback and outline for an extensible approach
Date: Mon, 7 Jul 2025 14:51:00 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>

>> * 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

view thread (79+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Adding basic NUMA awareness - Preliminary feedback and outline for an extensible approach
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox