<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/expanding-customer-notifications-for-clickhouse-managed-postgres-ibqackjpl" -->

---
title: Expanding Customer Notifications for ClickHouse Managed...
description: ClickHouse is adding five new customer notifications to Managed Postgres, covering inactive replication slots, planned switchovers, unplanned failovers,...
canonical: https://daily.dev/posts/expanding-customer-notifications-for-clickhouse-managed-postgres-ibqackjpl
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Expanding Customer Notifications for ClickHouse Managed Postgres | daily.dev
og:description: ClickHouse is adding five new customer notifications to Managed Postgres, covering inactive replication slots, planned switchovers, unplanned failovers,...
og:url: https://daily.dev/posts/expanding-customer-notifications-for-clickhouse-managed-postgres-ibqackjpl
og:image: https://api.daily.dev/og/posts/ibQACkJpL.png
og:image:alt: Expanding Customer Notifications for ClickHouse Managed Postgres
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Expanding Customer Notifications for ClickHouse Managed Postgres

**[ClickHouse](https://daily.dev/sources/clickhouse)** · 5 min read · 0 upvotes · 0 comments

## Summary

ClickHouse is adding five new customer notifications to Managed Postgres, covering inactive replication slots, planned switchovers, unplanned failovers, long-running transactions, and connection usage. The inactive-slot notification will identify slots with at least 10 GiB of unconfirmed WAL over a two-hour observation period; one customer case involved an unused replication slot retaining about 650 GB of transaction logs. The long-running transaction notification will warn about transactions open for at least two hours. The connection notification will warn when usage reaches 95% of the limit. These build on an earlier notification introduced in August that warns when storage usage passes 85%.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://clickhouse.com/blog/expanding-customer-notifications-managed-postgres>

## Questions this post answers

### What triggers an inactive replication slot alert in ClickHouse Managed Postgres?

The alert fires when a logical replication slot is observed inactive with at least 10 GiB of unconfirmed write-ahead log (WAL) data over a two-hour observation period. The notification includes the slot name for investigation. Slots belonging to ClickHouse's managed CDC service are excluded from this alert.

_Anyone tracking storage bloat from stale replication slots can follow database monitoring updates like this on daily.dev._

### At what connection usage percentage does ClickHouse Managed Postgres warn about hitting the connection limit?

It warns when connection usage reaches 95% of the configured limit, giving time to investigate before new application connections start failing. Causes often include per-instance connection pools multiplying as applications scale out, or idle sessions the application never returned to the pool.

_Teams debugging connection exhaustion can keep up with database alerting features like this via daily.dev._

### How can I avoid WAL buildup from logical replication slots when streaming Postgres data to ClickHouse?

Switching from logical replication slots to WalShadow avoids this problem, since WalShadow uses physical WAL replication instead of logical replication slots, eliminating the source of WAL buildup entirely. This matters for setups like ClickPipes that stream from Managed Postgres to ClickHouse for analytics using logical replication.

_Developers choosing a replication strategy for Postgres-to-ClickHouse pipelines can track tooling changes like this on daily.dev._

## Similar posts on daily.dev

- [All Your GUCs in a Row: max\_notify\_queue\_pages](https://daily.dev/posts/all-your-gucs-in-a-row-max-notify-queue-pages-h8vhu0wz4) · Planet PostgreSQL · 1 upvotes · 0 comments
- [Postgres LISTEN/NOTIFY actually scales](https://daily.dev/posts/postgres-listen-notify-actually-scales-wehhixojn) · Hacker News · 34 upvotes · 2 comments
- [Postgres wait events, now in Query Insights](https://daily.dev/posts/postgres-wait-events-now-in-query-insights-sdbknr20z) · ClickHouse · 2 upvotes · 0 comments

---

Tags: [#database](https://daily.dev/tags/database), [#postgresql](https://daily.dev/tags/postgresql), [#clickhouse](https://daily.dev/tags/clickhouse)

[View this post on daily.dev](https://daily.dev/posts/expanding-customer-notifications-for-clickhouse-managed-postgres-ibqackjpl)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Expanding Customer Notifications for ClickHouse Managed Postgres","url":"https://daily.dev/posts/expanding-customer-notifications-for-clickhouse-managed-postgres-ibqackjpl","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/expanding-customer-notifications-for-clickhouse-managed-postgres-ibqackjpl"},"datePublished":"2026-10-26T15:23:32.209Z","dateModified":"2026-10-26T15:24:02.985Z","description":"ClickHouse is adding five new customer notifications to Managed Postgres, covering inactive replication slots, planned switchovers, unplanned failovers,...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7c4434217699360499f1fa2e07dbc7fc?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7c4434217699360499f1fa2e07dbc7fc?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"ClickHouse","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"ClickHouse","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/clickhouse","url":"https://daily.dev/sources/clickhouse"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/expanding-customer-notifications-for-clickhouse-managed-postgres-ibqackjpl","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"database,postgresql,clickhouse","timeRequired":"PT5M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"ClickHouse","item":"https://daily.dev/sources/clickhouse"},{"@type":"ListItem","position":3,"name":"Expanding Customer Notifications for ClickHouse Managed Postgres"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/expanding-customer-notifications-for-clickhouse-managed-postgres-ibqackjpl#faq","mainEntity":[{"@type":"Question","name":"What triggers an inactive replication slot alert in ClickHouse Managed Postgres?","acceptedAnswer":{"@type":"Answer","text":"The alert fires when a logical replication slot is observed inactive with at least 10 GiB of unconfirmed write-ahead log (WAL) data over a two-hour observation period. The notification includes the slot name for investigation. Slots belonging to ClickHouse's managed CDC service are excluded from this alert. Anyone tracking storage bloat from stale replication slots can follow database monitoring updates like this on daily.dev."}},{"@type":"Question","name":"At what connection usage percentage does ClickHouse Managed Postgres warn about hitting the connection limit?","acceptedAnswer":{"@type":"Answer","text":"It warns when connection usage reaches 95% of the configured limit, giving time to investigate before new application connections start failing. Causes often include per-instance connection pools multiplying as applications scale out, or idle sessions the application never returned to the pool. Teams debugging connection exhaustion can keep up with database alerting features like this via daily.dev."}},{"@type":"Question","name":"How can I avoid WAL buildup from logical replication slots when streaming Postgres data to ClickHouse?","acceptedAnswer":{"@type":"Answer","text":"Switching from logical replication slots to WalShadow avoids this problem, since WalShadow uses physical WAL replication instead of logical replication slots, eliminating the source of WAL buildup entirely. This matters for setups like ClickPipes that stream from Managed Postgres to ClickHouse for analytics using logical replication. Developers choosing a replication strategy for Postgres-to-ClickHouse pipelines can track tooling changes like this on daily.dev."}}]}
```

