# Why strict memory overcommit matters for Postgres

DevFeed: [Why strict memory overcommit matters for Postgres](<https://devfeed.tech/articles/why-strict-memory-overcommit-matters-for-postgres-5582.md>)

Original publisher: [Read original article](<https://clickhouse.com/blog/strict-memory-overcommit-for-postgres>)

Author: Kaushik Iska

Published: 2026-07-28T00:00:00Z

Content type: article

Language: en

Sources: [ClickHouse Blog](<https://devfeed.tech/sources/clickhouse-blog.md>)

Topics: [clickhouse](<https://devfeed.tech/topics/clickhouse.md>), [Linux](<https://devfeed.tech/topics/linux.md>), [Processes](<https://devfeed.tech/topics/processes.md>), [Hardware](<https://devfeed.tech/topics/hardware.md>)

Tags: [clickhouse](<https://devfeed.tech/tags/clickhouse.md>), [linux](<https://devfeed.tech/tags/linux.md>), [memory](<https://devfeed.tech/tags/memory.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [processes](<https://devfeed.tech/tags/processes.md>)

## AI overview

The article explains why ClickHouse Managed Postgres uses strict Linux memory overcommit. Strict accounting turns a potentially instance-wide OOM restart into a single failed query while preserving other connections, with no measurable throughput cost.

## Source excerpt

Why ClickHouse Managed Postgres runs strict memory overcommit by default, and how it turns an instance-wide OOM restart into a single failed query -- shown side by side on identical hardware, with no measurable throughput cost.