PostgreSQL Minor Update Checker
A PostgreSQL minor update (for example 17.4 to 17.12) only needs new binaries and a restart, but many releases also say "you may need to reindex" or "take a new full backup" after updating, and those steps add up when you skip releases. Enter the version you run and this tool lists every update release between it and the latest one, with the official "Migration to Version X.Y" notes, the changelog entries that ask for a REINDEX or another manual step, the CVEs fixed, and tested SQL that finds the affected indexes. Data comes from the postgresql.org release notes for 14.1 to 18.7.
Do more than postgresql minor update checker — meet Chat2DB
Chat2DB is an AI-powered SQL client for Windows, macOS and Linux. Write SQL in natural language, format and optimize queries automatically, and manage MySQL, PostgreSQL, Oracle and 20+ other databases in one workspace.
How to use
- Run SELECT version(); or SHOW server_version; in psql (or check your cloud console) and paste the result, for example 17.4, PostgreSQL 16.2 on x86_64-pc-linux-gnu, or a server_version_num such as 170004.
- Read the summary: how many update releases you are behind, the latest minor for your branch, its end-of-life date and how many CVEs the skipped releases fix.
- Go through each skipped release's post-update steps, run the generated SQL in every database to find affected indexes, then copy the checklist for your change ticket.
Frequently asked questions
Do I need pg_upgrade or a dump and restore for a PostgreSQL minor update?
No. Update releases within one major version (17.4 to 17.12, for example) never change the on-disk format, so you install the new binaries and restart the server. The release notes call out extra steps when a bug fix cannot repair existing data by itself, most often a REINDEX of certain index types, an ANALYZE, or a new full backup. Those are the steps this tool collects.
I skipped several releases. Which post-update steps apply to me?
All of them. Update releases are cumulative for code, but a step such as reindexing ltree indexes in 18.2 is still needed if you jump straight from 18.1 to 18.7. That is why each release note ends with "if you are upgrading from a version earlier than X, see Section E.N". The checker lists every release between your version and the latest one so nothing is missed.
Is PostgreSQL 14 still supported after 14.25?
No. PostgreSQL 14 reached end of life on November 12, 2026, and 14.25 is its final release. Updating to 14.25 fixes the known bugs up to that date, but future security issues will not be fixed for 14, so plan a major version upgrade to 17 or 18. PostgreSQL 15 is supported until November 11, 2027.
