Skip to main content
ClickHouse 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.

Maintenance updates

Regular maintenance in the PostgreSQL instances includes the following:
  • 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.
These are performed via failover and typically result in only a brief disconnect, often lasting just a few seconds. For instances with standbys enabled, the upgrade is applied to the standby first, followed by a failover to minimize downtime.

Scheduled upgrades

By default, maintenance is applied to your instance whenever a new release is ready. With scheduled upgrades you choose a two-hour UTC window during which that maintenance may be applied, so the brief failover lands at the time that’s least disruptive to your workload. Expected downtime is less than 1 minute within the window. On the Enterprise plan you can also restrict upgrades to specific days of the week. On the Scale plan you choose the time period only, and upgrades may be applied on any day within it.

Configure a schedule

1

Open the instance settings

Select your instance, then select Settings from the left menu and scroll to the Configuration section.
2

Open the scheduled upgrades flyout

In the Scheduled upgrades subsection, select Configure schedule. If a schedule is already set, the current schedule is shown and the button reads Edit schedule.
3

Pick a time period

Select one of the twelve two-hour UTC windows from the Time period (UTC) list. A time period is required.
4

Optionally restrict the days

On the Enterprise plan, select one or more days under Day(s) of the week. Leave every day unselected to allow upgrades on any day within the time period.
5

Save

Select Save. The schedule takes effect immediately and is shown in the Scheduled upgrades subsection, for example Scheduled upgrades: Sat, Sun at 12:00 a.m. - 2:00 a.m. UTC.
You need the control-plane:postgres-service:manage permission on the instance to change its schedule. The controls are also disabled while an instance is stopped or is still being provisioned.

Time periods

Windows are two hours long and are always expressed in UTC — there’s no local-timezone selection. The available windows are: Custom start times, custom window lengths, and more than one window per instance aren’t supported.

Days of the week

Restricting the days is optional:
  • No days selected — upgrades may be applied on any day, inside the chosen time period.
  • One or more days selected — upgrades are only applied on those days, inside the chosen time period. Selecting all seven days is equivalent to selecting none.

What a schedule applies to

A schedule governs platform maintenance only — the minor version upgrades, managed service feature updates, and operating system patches described in Maintenance updates. Changes that you initiate yourself aren’t deferred to the window and are applied as soon as you make them. This includes scaling an instance, resizing storage, and changing configuration parameters.
Scheduled upgrades are best effort. Maintenance may be applied outside your window when it’s required for the health of your instance — for example when disk usage reaches 95% — or for critical security patches and vulnerability fixes. You’ll be notified of such exceptions as necessary.

Read replicas

Read replicas follow the schedule of their primary instance and don’t have a schedule of their own, so the Scheduled upgrades section isn’t shown for them.

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 to upgrade your ClickHouse Managed Postgres instance.
Last modified on August 24, 2026