Is Raising work_mem from 4 MB to 64 MB Really Optimizing Sorts? The 2 TB PostgreSQL OOM Time Bomb

The article explains why increasing PostgreSQL's work_mem does not guarantee per‑query memory limits, how multiple sort/hash nodes, parallel workers and long‑lived memory contexts can cause OOM even on a 2 TB server, and offers concrete diagnostics and mitigation strategies for DBAs and developers.

Memory ManagementOOMPostgreSQL

0 likes · 12 min read

Is Raising work_mem from 4 MB to 64 MB Really Optimizing Sorts? The 2 TB PostgreSQL OOM Time Bomb

ITPUB

Nov 10, 2024 · Databases

Why Oracle DBAs Must Rethink PostgreSQL’s work_mem and Cursor Sharing

The article explains how Oracle DBAs transitioning to PostgreSQL often misinterpret work_mem and cursor sharing, showing how improper settings can drastically change execution plans, increase query time, and cause performance issues, while also highlighting differences in memory management and plan caching between the two systems.

DBAOraclePostgreSQL

0 likes · 8 min read

Why Oracle DBAs Must Rethink PostgreSQL’s work_mem and Cursor Sharing

Is Raising work_mem from 4 MB to 64 MB Really Optimizing Sorts? The 2 TB PostgreSQL OOM Time Bomb

Why Oracle DBAs Must Rethink PostgreSQL’s work_mem and Cursor Sharing

Is Raising work_mem from 4 MB to 64 MB Really Optimizing Sorts? The 2 TB PostgreSQL OOM Time Bomb