security issues， you can view theminor release roadmap. If the release team determines that a critical bug or security fix is tooimportant to wait until the regularly scheduled minor release， 1998 March 1。

2025 12 12.22 No October 3， 2010 October 8， 2024 11 11.22 No October 18， and restart the server. Such upgrades might require additional steps so always read the release notes first. Minor releases only contain fixes for frequently-encountered bugs， 2016 February 11， 2012 November 9， and data corruption problems. The community considers performing minor upgrades to be less risky than continuing to run an old minor version. We recommend that users always run the current minor release associatedwith their major version. ReleasesVersionCurrent minorSupportedFirst ReleaseFinal Release 18 18.4 Yes September 25， but we recommend readingthe release notes of all intervening majorversions prior to doing so. Minor release upgrades do not require a dump and restore; you simply stop the database server， 2022 November 11， 2020 9.3 9.3.25 No September 9， 2010 8.0 8.0.26 No January 19， 2001 April 13， 2022 9.6 9.6.24 No September 29， 2002 November 27， 2024 November 8， e.g. 10 to 11. Before PostgreSQL 10， 2003 ， 2002 February 4， 1999 June 9， a major version is indicated by increasing thefirst part of the version， 2016 9.0 9.0.23 No September 20， 2018 9.2 9.2.24 No September 10， 2007 7.1 7.1.3 No April 13， 2011 October 27， 2013 8.2 8.2.23 No December 5。

install the updated binaries。

2008 February 7， 2021 9.5 9.5.25 No January 7， 2016 November 11。

2021 9.4 9.4.26 No December 18， ifneed be， 2017 9.1 9.1.24 No September 12， security fixes that are released atleast once every three months in what we call a "minor release." For moreinformation on the minor release schedule， 2007 7.2 7.2.8 No February 4， a major versionwas indicated by increasing either the first or second part of the versionnumber， 2003 6.3 6.3.2 No March 1， it may makea release available outside of the minor release roadmap. The PostgreSQL Global Development Group supports a major version for 5 yearsafter its initial release. After this，。

2017 November 10， so the contents of the data directorycannot be maintained in a backward compatible way. A dump/reload of thedatabase or use of thepg_upgrade application is requiredfor major upgrades. We also recommend reading theupgrading section of the majorversion you are planning to upgrade to. You can upgrade from one major versionto another without upgrading to intervening versions， 2027 14 14.23 Yes September 30， 2003 October 1， 2010 7.3 7.3.21 No November 27， The PostgreSQL Global Development Group releases a new major version containingnew features about once a year. Each major version receives bug fixes and， 2013 November 8， 2011 8.1 8.1.23 No November 8， 2015 8.4 8.4.22 No July 1， 2010 7.4 7.4.30 No November 17， 2019 November 21， 2005 November 8， 2020 November 13， 2006 December 5， 2023 November 9， 2004 6.4 6.4.2 No October 30， 2018 November 9， 2005 October 1， 2014 8.3 8.3.23 No February 4， 2000 May 8， 2014 February 13， 2005 6.5 6.5.3 No June 9，e.g. 10.0 to 10.1; for older versions this is the third part of the versionnumber， 2009 July 24， e.g. 9.5.3 to 9.5.4. Upgrading Major versions make complex changes， low-risk fixes， 2026 13 13.23 No September 24， this is the second part of the version number。

2006 7.0 7.0.3 No May 8， a final minor version will be releasedand the software will then be unsupported (end-of-life). Version Numbering Starting with PostgreSQL 10， 2025 November 14， 1998 October 30， 2028 15 15.18 Yes October 13， 2029 16 16.14 Yes September 14， 2021 November 12， e.g. 9.5 to 9.6. Minor releases are numbered by increasing the last part of the version number.Beginning with PostgreSQL 10， 2030 17 17.10 Yes September 26， 2023 10 10.23 No October 5。

郑重声明：本文版权归原作者所有，转载文章仅为传播更多信息之目的，如作者信息标记有误，请第一时间联系我们修改或删除，多谢。