Hi, The "Linux Memory Overcommit" section of the docs only talks about host-wide behavior (vm.overcommit_memory, oom_score_adj), but a lot of installations now run Postgres in containers, where a cgroup memory limit is what actually triggers the OOM killer, regardless of the host's overcommit settings.
The attached patch adds a short subsection covering this: how memory.max behaves with cgroup v2, what happens when a backend is killed, what counts towards the limit (including the huge pages caveat), and a pointer to the kernel documentation. The patch is against master, and the docs build cleanly here. This is my first contribution, so I'd appreciate any feedback on the wording or on things I should add or drop. Thanks, João Marcelo
v1-0001-doc-Document-Linux-cgroup-memory-limits.patch
Description: Binary data
