| ID | 7381 | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Title | 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) | |||||||||
| CI (CFBot) | Not processed | |||||||||
| Stats (from CFBot) | Unknown | |||||||||
| Tags | Docs Only | |||||||||
| Created | 2026-10-01 22:24:31 | |||||||||
| Last modified | 2026-10-01 22:24:53 (1 hour ago) | |||||||||
| Latest email | 2026-10-01 22:19:38 (1 hour ago) | |||||||||
| Status |
PG20-3 (2026-11-01 – 2026-11-30): Needs review
|
|||||||||
| Target version | ||||||||||
| Authors | Joao Detomini (joaodetomini) | |||||||||
| Reviewers | Become reviewer | |||||||||
| Committer | ||||||||||
| Links | ||||||||||
| Emails |
|
|||||||||
| History |
|