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
| Aspect | Details |
|---|---|
| Release Frequency | One major version approximately every 12 months |
| Support Duration | 5 years of active support for each major version |
| What Support Includes | Regular minor releases with bug fixes and security patches |
| End of Support | After 5 years, one final minor release is published, then no further updates |
| EOL Definition | The point when a major version no longer receives any updates or security fixes |
| Recommendation | Always run a major version that is within its 5-year support window |
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.
| Risk | Impact on Your System |
|---|---|
| Security Exposure | Known vulnerabilities remain unpatched, increasing the risk of data breaches |
| No Bug Fixes | Any issues discovered will not be resolved by the official community |
| Compatibility Problems | Newer operating systems, libraries, and tools may no longer work reliably |
| Compliance Issues | Many regulatory standards and security audits require actively supported software |
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.
FAQ
Q1: How long is each PostgreSQL major version supported?
Each major version receives official support for five years from its initial release date.
Q2: What is included in PostgreSQL support?
Support includes regular minor releases with bug fixes, security patches, and small improvements.
Q3: What does EOL mean for PostgreSQL?
EOL means the major version has reached the end of its 5-year support period and will no longer receive any updates.
Q4: Is it safe to run an EOL version in production?
It is not recommended. Running an unsupported version increases security and compatibility risks significantly.
Q5: When should I upgrade my PostgreSQL version?
You should plan the upgrade well before your current major version reaches the end of its five-year support window.
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:
| Method | Command |
|---|---|
| Inside psql (recommended) | |
| Command line | psql --version |
| Server binary | postgres --version |
Perform this check as part of your regular maintenance routine to confirm you are running a supported version.