ClickHouse says it is adding five notifications for Managed Postgres: inactive replication slots with at least 10 GiB of unconfirmed WAL over a two-hour observation period, planned switchovers, unplanned failovers, transactions open for at least two hours, and connection usage at 95% of the service limit.
ClickHouse Watch analysis
What happened
The company cites a customer example involving an inactive slot retaining about 650 GB of transaction logs.
ClickHouse says it is adding five notifications for Managed Postgres: inactive replication slots with at least 10 GiB of unconfirmed WAL over a two-hour observation period, planned switchovers, unplanned failovers, transactions open for at least two hours, and connection usage at 95% of the service limit. The company cites a customer example involving an inactive slot retaining about 650 GB of transaction logs.
Why it matters
If this account holds, it is a material change for the people and products named, not a routine product note.
Our read
If this account holds, it is a material change for the people and products named, not a routine product note.
What to watch
- The open test on this story, not a recap of the announcement.
- What actually changes for users if the reported move ships.
- Which named facts later reporting confirms or walks back. The useful change is who has to alter a product, a budget or a public line if the account holds. Treat the first claims as attributed reporting, then watch for a primary statement that locks them in or walks them back.
Discussion spark: Which warning would be most useful in your database operations: inactive replication slots, long-running transactions, or connection use nearing its limit?
Sources and evidence
- Source update (26 October 2026, 15:22 UTC)
not affiliated with or endorsed by ClickHouse