Upgrade the minor version

Apply a newer minor release of the same PostgreSQL major now, instead of waiting for the maintenance window.

Last updated 18 November 2026View as Markdown

Minor releases are bug and security fixes with no format change. They are applied in the maintenance window, or when you ask. Replace ewdb-0123456789ab with your database's id.

Prerequisites

  • In the console, also rds:DescribeDBInstances to open the database's page (without it the page is not found).
  • Permission for rds:ModifyDBInstance. Without it the console shows no upgrade button.
  • The database is available. Otherwise the request is refused with 409 "Cannot upgrade while the database is …".
  • Machines with a maintenance agent that answers. Machines built before in-place upgrades cannot be upgraded here; Maintenance says so, they get the current version when they are replaced, and the API refuses with 409 "… cannot be upgraded in place: built before in-place upgrades, or its agent is not answering".

Upgrade now

  1. Open the database, then choose the Maintenance tab. The table shows what each node runs, and the section says which newer minor is available.
  2. Choose Upgrade to version now.
  3. In the browser's confirmation, choose OK. The tab says "Upgrade requested; it starts within a minute."

Result

A cluster is upgraded one node at a time: replicas first, each streaming again before the next. Leadership then moves by switchover to an upgraded node, and the old leader is upgraded last. Writes pause for a few seconds during the switchover. A single node restarts once and is unavailable for that restart.

The database is maintenance meanwhile, and each step is on Activity (phase upgrade), ending with "PostgreSQL … on every node". If a step fails, the database returns to available, the event "The upgrade to … stopped: …" says which node runs which version, and asking again finishes the rest: nodes already on the target are skipped.

Did this page help you?