PostgreSQL Release History & EOL Status

PostgreSQL Lifecycle & End of Life (EOL) Policy

PostgreSQL follows a clear and predictable release policy. A new major version is released approximately once per year, and each major version receives official support for five years from its initial release date.

During the support period, the PostgreSQL Global Development Group regularly releases minor versions containing bug fixes, security patches, and small improvements. After five years, support ends and the version is considered EOL (End of Life).

PostgreSQL Support Lifecycle Overview

This structured approach gives organizations a reliable timeline for planning upgrades and helps ensure long-term database security and stability.

Risks of Using End-of-Life (EOL) Versions

Continuing to use a PostgreSQL major version after its five-year support period carries increasing risks.

These risks often grow gradually but can become critical during security incidents or infrastructure upgrades.

What Happens After PostgreSQL Reaches EOL

When a major version reaches the end of its support period, the PostgreSQL Global Development Group publishes one final minor release and then stops all maintenance. No additional bug fixes or security patches will be provided.

Your database will still function in the short term, but it gradually becomes more vulnerable. Over time, compatibility with modern environments decreases, and any newly discovered security issues remain unaddressed. Maintaining such a system becomes more difficult and costly as the community and ecosystem move forward.

Planning a major version upgrade before the support window closes is the safest and most cost-effective strategy.

Tracking & Monitoring PostgreSQL EOL Dates

Because PostgreSQL follows a consistent five-year support policy, tracking is relatively straightforward. The best practice is to note the release year of your current major version and mark the approximate end-of-support date five years later.

Many organizations include PostgreSQL version checks in their monitoring tools or CI/CD pipelines. Regular reviews during quarterly planning help ensure no production environment approaches EOL unexpectedly.

Proactive tracking turns version management into a simple, routine process.

How To Check Your PostgreSQL Version

Checking your PostgreSQL version is quick and should be done regularly. Here are the most reliable methods:

SELECT version();

Perform this check as part of your regular maintenance routine to confirm you are running a supported version.