Skip to content

docs: rework Managed Postgres upgrades section for Beta #64

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mintlify wants to merge 2 commits into
base: main
Choose a base branch
from
+16 −6
Open

docs: rework Managed Postgres upgrades section for Beta #64

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
cdb0256
docs: rework Managed Postgres upgrades section for Beta
mintlify[bot] May 26, 2026
4eac24d
docs: apply post-merge fixes to Managed Postgres upgrades
mintlify[bot] May 27, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 16 additions & 6 deletions products/managed-postgres/upgrades.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,16 +13,26 @@ import PrivatePreviewBadge from "/snippets/components/PrivatePreviewBadge/Privat

Managed Postgres handles PostgreSQL version upgrades to keep your instances secure and up to date. Both minor and major version upgrades are supported with minimal disruption.

## Minor version upgrades {#minor-version-upgrades}
## Maintenance updates {#maintenance-updates}

Minor version upgrades (e.g., 16.4 to 16.5) include bug fixes and security patches. These are performed via failover and typically result in only a brief disconnect, often lasting just a few seconds.
Regular maintenance in the PostgreSQL instances includes the following:

For instances with [standbys](/products/managed-postgres/high-availability) enabled, the upgrade is applied to the standby first, followed by a failover to minimize downtime.
- Minor version upgrades (e.g., 17.4 to 17.5) include bug fixes and PostgreSQL engine security patches.
- Managed Service features. Improvements to native CDC, observability, pg_clickhouse, and other extensions.
- Operating system and system components patches. Including security fixes, efficiency, and other improvements.

## Major version upgrades {#major-version-upgrades}
These are performed via failover and typically result in only a brief disconnect, often lasting just a few seconds.

Major version upgrades (e.g., 16.x to 17.x) also involve only a few seconds of downtime, following a similar failover-based approach.
For instances with [standbys](/products/managed-postgres/high-availability) enabled, the upgrade is applied to the standby first, followed by a failover to minimize downtime.

## Maintenance windows {#maintenance-windows}

Managed Postgres supports maintenance windows so that upgrades and other maintenance operations can be scheduled at a time that's least disruptive to your workload. UI support for configuring maintenance windows is coming soon. In the meantime, contact [support](https://clickhouse.com/support/program) to set up a maintenance window for your instance.
Default maintenance window is 14:00 to 16:00 UTC on Sunday.
Expected downtime is less than 1 minute within the window.

For Enterprise Tier organizations, Managed Postgres supports maintenance windows so that upgrades and other maintenance operations can be scheduled at a time that's least disruptive to your workload. UI and API support for configuring maintenance windows is coming soon. In the meantime, contact [support](https://clickhouse.com/support/program) to set up a maintenance window for your instance.

## Major version upgrades {#major-version-upgrades}

Major version upgrades (e.g., 17.x to 18.x) via UI and API are coming soon.
In the meantime, contact [support](https://clickhouse.com/support/program) to upgrade your Managed Postgres instance.