How we configure huge pages in ClickHouse Managed Postgres

T1Covered by 1 source · first reported by Databricks / ClickHouse / DuckDB / Supabase / Neon / PlanetScale at 14 Jul, 14:59 UTC

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.

Sources

• T1How we configure huge pages in ClickHouse Managed PostgresDatabricks / ClickHouse / DuckDB / Supabase / Neon / PlanetScale14 Jul, 14:59