PostgreSQL supports each major version for five years. Version 14’s final release is scheduled for November 12, 2026, version 13 is already unsupported, and moving to 15 through 18 needs a dump and reload or pg_upgrade rather than a simple minor update.
\nThe PostgreSQL versioning policy says the project supports a major version for 5 years after its initial release, then issues a final minor version, after which it is unsupported. Its release table lists version 14 as supported with a final release of November 12, 2026, and version 13 as unsupported after November 13, 2025.
\nSupported versions 15, 16, 17 and 18 have final releases scheduled for November 11, 2027, November 9, 2028, November 8, 2029 and November 14, 2030. Minor releases with bug and security fixes come at least once every three months, and the project recommends always running the current minor release.
\nMajor upgrades cannot keep the data directory backward compatible, so they require a dump and reload or pg_upgrade. Upgrades may skip intervening major versions, but the project recommends reading the release notes of every version in between. Minor upgrades only need the server stopped, binaries updated and the server restarted.
\nUse this for self-managed PostgreSQL and for products that embed it. Hosted database services and appliance vendors may follow different schedules, so confirm their end-of-support dates for the version you run.
\nDSE recommends identifying every PostgreSQL 13 and 14 instance and scheduling a tested major-version upgrade before November 12, 2026. Restore a recent backup to a test server, run pg_upgrade or a dump and reload against it, and test the application, including vendor-supplied software, before upgrading production. Ask application vendors which PostgreSQL versions they certify before choosing a target.
\nQuery each server’s version, record it with its owner and application, and confirm after the upgrade that the new version is current on its latest minor release. Keep the pre-upgrade backup until the application has run cleanly for an agreed period.
\nPostgreSQL Global Development Group — Versioning Policy. Reviewed October 18, 2026.
", "content_text": "PostgreSQL supports each major version for five years. Version 14’s final release is scheduled for November 12, 2026, version 13 is already unsupported, and moving to 15 through 18 needs a dump and reload or pg_upgrade rather than a simple minor update.\nSource facts\nThe PostgreSQL versioning policy says the project supports a major version for 5 years after its initial release, then issues a final minor version, after which it is unsupported. Its release table lists version 14 as supported with a final release of November 12, 2026, and version 13 as unsupported after November 13, 2025.\nSupported versions 15, 16, 17 and 18 have final releases scheduled for November 11, 2027, November 9, 2028, November 8, 2029 and November 14, 2030. Minor releases with bug and security fixes come at least once every three months, and the project recommends always running the current minor release.\nMajor upgrades cannot keep the data directory backward compatible, so they require a dump and reload or pg_upgrade. Upgrades may skip intervening major versions, but the project recommends reading the release notes of every version in between. Minor upgrades only need the server stopped, binaries updated and the server restarted.\nApplicability\nUse this for self-managed PostgreSQL and for products that embed it. Hosted database services and appliance vendors may follow different schedules, so confirm their end-of-support dates for the version you run.\nDSE recommendation\nDSE recommends identifying every PostgreSQL 13 and 14 instance and scheduling a tested major-version upgrade before November 12, 2026. Restore a recent backup to a test server, run pg_upgrade or a dump and reload against it, and test the application, including vendor-supplied software, before upgrading production. Ask application vendors which PostgreSQL versions they certify before choosing a target.\nVerification\nQuery each server’s version, record it with its owner and application, and confirm after the upgrade that the new version is current on its latest minor release. Keep the pre-upgrade backup until the application has run cleanly for an agreed period.\nOfficial reference\nPostgreSQL Global Development Group — Versioning Policy. Reviewed October 18, 2026.", "content_markdown": "PostgreSQL supports each major version for five years. Version 14’s final release is scheduled for November 12, 2026, version 13 is already unsupported, and moving to 15 through 18 needs a dump and reload or pg_upgrade rather than a simple minor update.\n\n## Source facts\n\nThe [PostgreSQL versioning policy](https://www.postgresql.org/support/versioning/) says the project supports a major version for 5 years after its initial release, then issues a final minor version, after which it is unsupported. Its release table lists version 14 as supported with a final release of November 12, 2026, and version 13 as unsupported after November 13, 2025.\n\nSupported versions 15, 16, 17 and 18 have final releases scheduled for November 11, 2027, November 9, 2028, November 8, 2029 and November 14, 2030. Minor releases with bug and security fixes come at least once every three months, and the project recommends always running the current minor release.\n\nMajor upgrades cannot keep the data directory backward compatible, so they require a dump and reload or pg_upgrade. Upgrades may skip intervening major versions, but the project recommends reading the release notes of every version in between. Minor upgrades only need the server stopped, binaries updated and the server restarted.\n\n## Applicability\n\nUse this for self-managed PostgreSQL and for products that embed it. Hosted database services and appliance vendors may follow different schedules, so confirm their end-of-support dates for the version you run.\n\n## DSE recommendation\n\nDSE recommends identifying every PostgreSQL 13 and 14 instance and scheduling a tested major-version upgrade before November 12, 2026. Restore a recent backup to a test server, run pg_upgrade or a dump and reload against it, and test the application, including vendor-supplied software, before upgrading production. Ask application vendors which PostgreSQL versions they certify before choosing a target.\n\n## Verification\n\nQuery each server’s version, record it with its owner and application, and confirm after the upgrade that the new version is current on its latest minor release. Keep the pre-upgrade backup until the application has run cleanly for an agreed period.\n\n## Official reference\n\n[PostgreSQL Global Development Group — Versioning Policy](https://www.postgresql.org/support/versioning/). Reviewed October 18, 2026." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/postgresql-14-end-of-life-november-12-2026-upgrade-planning/", "url": "https://update.dsesecurity.com/updates/postgresql-14-end-of-life-november-12-2026-upgrade-planning/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-18" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/postgresql-14-end-of-life-november-12-2026-upgrade-planning/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "PostgreSQL 14’s final release is November 12, 2026: plan the major upgrade before support ends", "item": "https://update.dsesecurity.com/updates/postgresql-14-end-of-life-november-12-2026-upgrade-planning/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/postgresql-14-end-of-life-november-12-2026-upgrade-planning/#article", "identifier": "https://update.dsesecurity.com/updates/postgresql-14-end-of-life-november-12-2026-upgrade-planning/", "url": "https://update.dsesecurity.com/updates/postgresql-14-end-of-life-november-12-2026-upgrade-planning/", "headline": "PostgreSQL 14’s final release is November 12, 2026: plan the major upgrade before support ends", "description": "PostgreSQL supports each major version for five years. Version 14’s final release is scheduled for November 12, 2026, version 13 is already…", "abstract": "PostgreSQL supports each major version for five years. Version 14’s final release is scheduled for November 12, 2026, version 13 is already unsupported, and moving to 15 through 18 needs a dump and reload or pg_upgrade rather than a simple minor update.", "articleBody": "PostgreSQL supports each major version for five years. Version 14’s final release is scheduled for November 12, 2026, version 13 is already unsupported, and moving to 15 through 18 needs a dump and reload or pg_upgrade rather than a simple minor update.\nSource facts\nThe PostgreSQL versioning policy says the project supports a major version for 5 years after its initial release, then issues a final minor version, after which it is unsupported. Its release table lists version 14 as supported with a final release of November 12, 2026, and version 13 as unsupported after November 13, 2025.\nSupported versions 15, 16, 17 and 18 have final releases scheduled for November 11, 2027, November 9, 2028, November 8, 2029 and November 14, 2030. Minor releases with bug and security fixes come at least once every three months, and the project recommends always running the current minor release.\nMajor upgrades cannot keep the data directory backward compatible, so they require a dump and reload or pg_upgrade. Upgrades may skip intervening major versions, but the project recommends reading the release notes of every version in between. Minor upgrades only need the server stopped, binaries updated and the server restarted.\nApplicability\nUse this for self-managed PostgreSQL and for products that embed it. Hosted database services and appliance vendors may follow different schedules, so confirm their end-of-support dates for the version you run.\nDSE recommendation\nDSE recommends identifying every PostgreSQL 13 and 14 instance and scheduling a tested major-version upgrade before November 12, 2026. Restore a recent backup to a test server, run pg_upgrade or a dump and reload against it, and test the application, including vendor-supplied software, before upgrading production. Ask application vendors which PostgreSQL versions they certify before choosing a target.\nVerification\nQuery each server’s version, record it with its owner and application, and confirm after the upgrade that the new version is current on its latest minor release. Keep the pre-upgrade backup until the application has run cleanly for an agreed period.\nOfficial reference\nPostgreSQL Global Development Group — Versioning Policy. Reviewed October 18, 2026.", "datePublished": "2026-10-18T21:00:49+00:00", "dateModified": "2026-10-18T22:22:07+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/postgresql-14-end-of-life-november-12-2026-upgrade-planning/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/postgresql-14-end-of-life-november-12-2026-upgrade-planning/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "PostgreSQL 14’s final release is November 12, 2026: plan the major upgrade before support ends" }, "articleSection": [ "Business Continuity", "IT" ], "keywords": [ "Business Continuity", "IT", "Briefing", "Important priority" ], "genre": "Briefing", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 317, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "PostgreSQL Global Development Group — Versioning Policy", "url": "https://www.postgresql.org/support/versioning/" } } ] } }