# How we configure huge pages in ClickHouse Managed Postgres

DevFeed: [How we configure huge pages in ClickHouse Managed Postgres](<https://devfeed.tech/articles/how-we-configure-huge-pages-in-clickhouse-managed-postgres-5307.md>)

Original publisher: [Read original article](<https://clickhouse.com/blog/huge-pages-clickhouse-managed-postgres>)

Author: Kaushik Iska

Published: 2026-07-14T14:59:25Z

Content type: article

Language: en

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

Topics: [clickhouse](<https://devfeed.tech/topics/clickhouse.md>), [Back end](<https://devfeed.tech/topics/backend.md>), [cpu](<https://devfeed.tech/topics/cpu.md>), [configuration](<https://devfeed.tech/topics/configuration.md>), [Provisioning](<https://devfeed.tech/topics/provisioning.md>), [Processes](<https://devfeed.tech/topics/processes.md>)

Tags: [backend](<https://devfeed.tech/tags/backend.md>), [clickhouse](<https://devfeed.tech/tags/clickhouse.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [memory](<https://devfeed.tech/tags/memory.md>), [os](<https://devfeed.tech/tags/os.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [server](<https://devfeed.tech/tags/server.md>)

## AI overview

ClickHouse Managed Postgres uses huge pages to reduce page-table memory overhead and improve translation coverage for its shared buffer cache. The article explains how the service reserves huge pages before startup, refuses to run when the reservation is unavailable, verifies usage, and sizes shared_buffers to fit the reserved pool.

## Source excerpt

How ClickHouse Managed Postgres reserves, enforces, and sizes huge pages so shared_buffers avoids the per-connection page-table tax that eats RAM and stalls reads on 4KB pages.