ClickHouse explains why Postgres shared_buffers gets costlier as connections rise
arpit_bhayani · x · 2026-07-27
A reference to a ClickHouse blog explains why Postgres sharedbuffers gets more expensive as connection count rises:
- Each backend process maps the shared buffer segment through its own page tables.
- Linux/OS memory is managed in 4 KB pages, so more connections mean more page-table entries and more overhead.
- The post points readers to the ClickHouse write-up for the deeper explanation.
Related event: Why Postgres Shared Buffers Get Pricier with More Connections(2 posts)→
More from Infra
- Google’s AlloyDB Omni demo runs fully offline with Gemma and TimesFM — rseroter · 2026-07-28
- SSI Signs $410M Compute Deal with Amazon, Bulk of Its Fundraising — TechCrunch AI · 2026-07-28
- Taiwan Detains Nvidia Employee in Widening AI Server Smuggling Probe — The Decoder · 2026-07-28
- RBC says a DIY AI replacement for Office could cost 11 times more over five years — TiernanRayTech · 2026-07-28
- LangChain says its NVIDIA partnership helps enterprises own domain intelligence — LangChain · 2026-07-28
- Alabama shelter sues to block AI data center 500 feet away over heat and noise risks — Polymarket · 2026-07-28