| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Cédric Villemain <cedric(dot)villemain(at)data-bene(dot)io> |
| Cc: | Tomas Vondra <tomas(at)vondra(dot)me>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Adding basic NUMA awareness - Preliminary feedback and outline for an extensible approach |
| Date: | 2025-07-07 23:25:35 |
| Message-ID: | cwp57ttiqplhbobl74obmry4gjwtqhdh5omm7fhwgdvft4qg4q@jmpveobozjhj |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2025-07-05 07:09:00 +0000, Cédric Villemain wrote:
> In my work on more careful PostgreSQL resource management, I've come to the
> conclusion that we should avoid pushing policy too deeply into the
> PostgreSQL core itself. Therefore, I'm quite skeptical about integrating
> NUMA-specific management directly into core PostgreSQL in such a way.
I think it's actually the opposite - whenever we pushed stuff like this
outside of core it has hurt postgres substantially. Not having replication in
core was a huge mistake. Not having HA management in core is probably the
biggest current adoption hurdle for postgres.
To deal better with NUMA we need to improve memory placement and various
algorithms, in an interrelated way - that's pretty much impossible to do
outside of core.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2025-07-07 23:38:41 | Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) |
| Previous Message | Tomas Vondra | 2025-07-07 22:35:43 | Re: Adding basic NUMA awareness - Preliminary feedback and outline for an extensible approach |