https://www.postgresql.org/support/versioning/
Versioning Policy
The PostgreSQL Global Development Group releases a new major version containing new features about once a year. Each major version receives bug fixes and, if need be, security fixes that are released at least once every three months in what we call a "minor release." For more information on the minor release schedule, you can view the minor release roadmap.
If the release team determines that a critical bug or security fix is too important to wait until the regularly scheduled minor release, it may make a release available outside of the minor release roadmap.
The PostgreSQL Global Development Group supports a major version for 5 years after its initial release. After its five year anniversary, a major version will have one last minor release containing any fixes and will be considered end-of-life (EOL) and no longer supported.
Version Numbering
Starting with PostgreSQL 10, a major version is indicated by increasing the first part of the version, e.g. 10 to 11. Before PostgreSQL 10, a major version was indicated by increasing either the first or second part of the version number, e.g. 9.5 to 9.6.
Minor releases are numbered by increasing the last part of the version number. Beginning with PostgreSQL 10, this is the second part of the version number, e.g. 10.0 to 10.1; for older versions this is the third part of the version number, e.g. 9.5.3 to 9.5.4.
Upgrading
We always recommend that all users run the latest available minor release for whatever major version is in use.
Major versions usually change the internal format of system tables and data files. These changes are often complex, so we do not maintain backward compatibility of all stored data. A dump/reload of the database or use of the pg_upgrade module is required for major upgrades. We also recommend reading the upgrading section of the major version you are planning to upgrade to.
Upgrading to a minor release does not normally require a dump and restore; you can stop the database server, install the updated binaries, and restart the server. For some releases, manual changes may be required to complete the upgrade, so always read the release notes before upgrading.
While upgrading will always contain some level of risk, PostgreSQL minor releases fix only frequently-encountered bugs, security issues, and data corruption problems to reduce the risk associated with upgrading. For minor releases, the community considers not upgrading to be riskier than upgrading.
Releases
| Version | Current minor | Supported | First Release | Final Release |
|---|---|---|---|---|
| 13 | 13.1 | Yes | September 24, 2020 | November 13, 2025 |
| 12 | 12.5 | Yes | October 3, 2019 | November 14, 2024 |
| 11 | 11.10 | Yes | October 18, 2018 | November 9, 2023 |
| 10 | 10.15 | Yes | October 5, 2017 | November 10, 2022 |
| 9.6 | 9.6.20 | Yes | September 29, 2016 | November 11, 2021 |
| 9.5 | 9.5.24 | Yes | January 7, 2016 | February 11, 2021 |
| 9.4 | 9.4.26 | No | December 18, 2014 | February 13, 2020 |
| 9.3 | 9.3.25 | No | September 9, 2013 | November 8, 2018 |
| 9.2 | 9.2.24 | No | September 10, 2012 | November 9, 2017 |
| 9.1 | 9.1.24 | No | September 12, 2011 | October 27, 2016 |
| 9.0 | 9.0.23 | No | September 20, 2010 | October 8, 2015 |
| 8.4 | 8.4.22 | No | July 1, 2009 | July 24, 2014 |
| 8.3 | 8.3.23 | No | February 4, 2008 | February 7, 2013 |
| 8.2 | 8.2.23 | No | December 5, 2006 | December 5, 2011 |
| 8.1 | 8.1.23 | No | November 8, 2005 | November 8, 2010 |
| 8.0 | 8.0.26 | No | January 19, 2005 | October 1, 2010 |
| 7.4 | 7.4.30 | No | November 17, 2003 | October 1, 2010 |
| 7.3 | 7.3.21 | No | November 27, 2002 | November 27, 2007 |
| 7.2 | 7.2.8 | No | February 4, 2002 | February 4, 2007 |
| 7.1 | 7.1.3 | No | April 13, 2001 | April 13, 2006 |
| 7.0 | 7.0.3 | No | May 8, 2000 | May 8, 2005 |
| 6.5 | 6.5.3 | No | June 9, 1999 | June 9, 2004 |
| 6.4 | 6.4.2 | No | October 30, 1998 | October 30, 2003 |
| 6.3 | 6.3.2 | No | March 1, 1998 | March 1, 2003 |