PostgreSQL work_mem Configuration Pitfalls: How Low Memory Settings Can Cause Catastrophic Outages
My friend Henrietta Dombrovskaya pinged me on Telegram. Her production cluster had just been killed by the OOM killer after eating 2 TB of RAM. work_mem was set to 2 MB. Something didn’t add up…
Read the full articleYou might also wanna read
PostgreSQL positioned as a solution to AI-driven datacenter energy demands
A billion AI agents walk into a power grid
theregister.com·1mo agoOutgrowing Postgres: Handling growing data volumes
Postgres slowing down at terabyte scale? Before you migrate, try these optimization techniques. And know when it's time to move on.
PostgreSQL 19 to switch default TOAST compression to LZ4 for faster performance
This week's database news covers three notable developments across the SQLite and PostgreSQL ecosystems. SQLite developers are debating the
PostgreSQL Double Buffering: Why OS RAM and Buffer Cache Compete and How the 25% Rule Helps
Learn how PostgreSQL double buffering wastes RAM, increases latency, and hurts query performance — plus the 25% shared_buffers rule to fix i
Outgrowing Postgres: How to run OLAP workloads on Postgres
A deep dive into running analytics on Postgres, from basic optimizations to advanced techniques and knowing when to quit.
Engineers Detail Technical Hurdles of Rewriting PostgreSQL Database Engine in Rust
Developers attempting to rewrite PostgreSQL in Rust have documented significant technical challenges, including a 12–15% CPU overhead introd
Comments
Sign in to join the conversation.
No comments yet. Be the first.