work_mem: it's a trap!
Summary
The article analyzes a PostgreSQL memory trap where a small per-operation memory limit (work_mem) can balloon memory usage when many allocations persist for the duration of a query. It presents a practical debugging approach using pg_log_backend_memory_contexts, explains why memory isn’t released per operation, and offers concrete remediation steps to prevent OOM incidents and improve query design.