Why PostgreSQL Enforces Strict Memory Overcommit to Dodge OOM‑Induced Outages
Linux’s OOM killer can terminate a single PostgreSQL backend, corrupting shared memory and forcing the whole cluster to restart. By enabling strict overcommit, PostgreSQL forces the kernel to reject impossible allocations early, preventing silent data corruption and long downtime. The post also shows a heuristic for setting the overcommit limit.