# Versions and maintenance

Which PostgreSQL versions are offered, how minor releases and their extension builds are pinned, and what happens in the maintenance window.

## Versions offered

PostgreSQL **15, 16, 17 and 18** are offered. 17 is the default. At creation, pass a major
(`"engineVersion": "18"`) for its newest offered minor, or an exact offered minor:

| Major | Offered minors   |
| ----- | ---------------- |
| 18    | `18.7`           |
| 17    | `17.12`, `17.11` |
| 16    | `16.16`          |
| 15    | `15.20`          |

Anything else is refused. 14 is not offered: its community support ended on 2026-11-12. 19 is not
offered.

You can pick an older offered minor at creation (`engineVersion: "17.11"`). New machines in an
existing database (readers, replacements) install the minor the database runs.

## Minor releases and their extension builds

New minor releases (bug and security fixes, no format change) are applied in the database's
maintenance window, or when you ask: see [Upgrade the minor version](upgrade-the-minor-version.md).

Each minor comes with a fixed set of extension builds, the ones every catalog extension was checked
to load with. Every machine of that minor installs exactly that set, whenever it is built, so a
replacement or a reader built months later has the same PostGIS, timescaledb and so on as the
machine it joins. Every minor is checked daily and on every change: it is installed exactly as a
new machine installs it, and `CREATE EXTENSION` runs for every catalog extension.

PGDG, where the packages come from, rebuilds extensions for the newest minor, and those builds do
not load on older ones. Since 2026-11-15, 18.6, 18.4, 17.10, 17.9, 16.15, 16.14, 15.19 and 15.18 are
no longer offered for new databases. Databases running them keep running, their new machines
install the extension builds recorded for their minor, and they move to the offered minor in their
maintenance window. A machine built before extension builds were pinned to its minor may have a
PostGIS built for a newer minor, and then `CREATE EXTENSION postgis` fails with "undefined symbol".
Upgrade the minor, or ask support to reinstall the database's extension builds.

## Major versions

A database moves to a newer major only when you ask: see
[Upgrade the major version](upgrade-the-major-version.md). There is no downgrade in place.

## The maintenance window

Every database has a weekly maintenance window, `sun:05:00-sun:06:00` UTC by default. Two things
happen in it:

- **Minor upgrades**, when automatic minor upgrades are on (the default). An upgrade starts only
  with enough of the window left to finish, and a running one is never cut off.
- **OS patch reboots.** Ubuntu security updates install on every node each night. When one needs a
  reboot (a kernel, libc), the node reboots in the window, one node at a time: replicas first, each
  back and streaming before the next, then a switchover to a rebooted replica, and the old leader
  last. A single node reboots in the window, so the database is unavailable for that reboot. The
  **OS patches** section of the **Maintenance** tab shows each node's state and why a reboot is
  waiting.

Machines built before in-place upgrades cannot be upgraded in place. **Maintenance** says so, and
they get the current version when they are replaced.

## Related

- [Set the maintenance window](set-the-maintenance-window.md)
- [Upgrade the minor version](upgrade-the-minor-version.md)
- [Upgrade the major version](upgrade-the-major-version.md)
