Version and support policy
PostgreSQL major/minor semantics, lifecycle, and choosing a version in 2026
Version meaning
Since PostgreSQL 10, the first number is the major, such as 18; the dotted number is the minor, such as 18.4. A major arrives roughly yearly with features. A minor contains bug, security, and low-risk fixes.
A minor update does not require dump/restore; it usually replaces binaries and restarts, though its release notes still apply. Data directories are incompatible across majors, requiring pg_upgrade, logical dump/restore, or logical replication migration.
Current support snapshot
As of 2026-08-02:
| Major | Current minor | Status | Final support date |
|---|---|---|---|
| 18 | 18.4 | Supported | 2030-11-14 |
| 17 | 17.10 | Supported | 2029-11-08 |
| 16 | 16.14 | Supported | 2028-11-09 |
| 15 | 15.18 | Supported | 2027-11-11 |
| 14 | 14.23 | Supported, near EOL | 2026-11-12 |
Source: official PostgreSQL versioning policy. Treat that live page as authoritative.
Upstream versions are not distribution package versions
Package snapshot evidence · PkgSeek
Sample default postgresql packages across distributions
| Distribution | Release | Indexed version | Repository | Linked advisories |
|---|---|---|---|---|
| Alibaba Cloud Linux | 3 | 13.23-3.0.1.al8 | official / updates | 0 |
| Alibaba Cloud Linux | 4 | 15.18-1.alnx4 | official / updates | 0 |
| AlmaLinux | 10 | 16.14-1.el10_2 | official / AppStream | 0 |
| AlmaLinux | 9 | 18.4-2.module_el9.8.0+280+5ad12178 | official / AppStream | 0 |
| Arch | rolling | 18.4-3 | official / extra | 0 |
| CentOS Stream | 10 | 16.14-1.el10 | official / AppStream | 0 |
| CentOS Stream | 9 | 13.23-3.el9 | official / AppStream | 0 |
| Debian | trixie | 17+278 | official / main | 3 |
| deepin | 25.2 | 16+255 | official / main | 0 |
| Fedora | 42 | 16.13-1.fc42 | official / updates | 0 |
| Fedora | 43 | 18.3-2.fc43 | official / updates | 0 |
| Fedora | 44 | 18.3-2.fc44 | official / updates | 0 |
Distributions may freeze a major and record packaging revisions or backported security fixes in complete versions such as 16.14-1.el10_2 or 18+290ubuntu1. Do not decide vulnerability status from the leading 16 or 18 alone. Identify the distribution, release, repository, architecture, and complete package version, then verify the vendor advisory.
Choosing for a new system
Default to the latest minor of the latest stable major unless a driver, extension, managed platform, or organizational certification is not ready. A conservative choice is a major with ample support runway that your workload has tested—not a near-EOL version chosen merely because it feels old.
PostgreSQL 19 is still in its beta cycle in August 2026 and is not a production default. Test a new major against extensions, collations, backup tools, pools, ORM, plans, and monitoring collectors.
See the PostgreSQL 19 release and 18-to-19 upgrade guide for the current Beta status, feature changes, and migration risks.
Keep the matrix in the repository
postgresql:
supported_majors: [17, 18]
tested_minor_floor:
17: 17.10
18: 18.4
extensions:
vector: "tested in CI"
upgrade_owner: platform-database
next_review: 2026-11-01latest is not a deployment strategy. Pin auditable images/packages and let a dependency process advance minors.
Upgrade principles
- Run the current minor of the chosen major; remaining on an old minor is often riskier than updating.
- Read all release notes across the version span.
- Test application behavior and plans on a restored real-data copy.
- Extensions have separate versions and upgrade scripts; inspect each one.
- Refresh statistics and validate backups after a major cutover.
Last updated on