AdminsForum
Newsroomby AdminsForum

What matters to the people running the Internet.

Join the forum
← All stories
Databases

PostgreSQL patch wave creates two upgrade decisions for database administrators

The November database updates combine urgent maintenance with a longer-term support decision. Hosting customers also need to distinguish upstream releases from their provider’s rollout.

2 min read Not rated yet
Original illustration of a database stack

PostgreSQL’s 12 November maintenance releases bring an unusually large collection of fixes, while the same announcement closes the community support window for PostgreSQL 14. Administrators therefore face two separate jobs: applying the relevant fixes and planning the future of installations on the retiring branch.

The released maintenance versions are 18.7, 17.12, 16.16, 15.20 and 14.25. The project reports 52 security fixes and more than 140 bug fixes. PostgreSQL 19 RC 2 was released alongside them, but it remains a release candidate rather than a final production release.

Installing packages is only part of the work

The PostgreSQL 18.7 release notes identify cases in which indexes may need rebuilding. They also recommend starting a new full-backup baseline after updating systems that use incremental backups. These are workload-specific follow-up tasks; a successful package update alone does not demonstrate that every database has completed its maintenance.

For PostgreSQL 14, installing 14.25 addresses the final community update. It does not extend that branch’s community support. Any separate support offered by a distribution or hosting provider needs checking against that provider’s own terms.

Hosted databases have a separate rollout

Clever Cloud announced the new versions for new add-ons and migrations on 13 November. Its migration guidance also describes a PostgreSQL 18 constraint condition that can stop a migration and trigger a rollback. That is a provider-specific workflow, not evidence that every managed database elsewhere has already updated.

AdminsForum perspective

Keep immediate patching and major-version migration as separate, documented decisions. Confirm the running branch, extension compatibility, backup recovery and the vendor’s post-update instructions before closing the maintenance ticket. A release announcement establishes availability; the running service and completed checks establish what your application is actually using.

Was this article useful?

Not rated yet

Sign in to rate this article. Ratings are from registered readers.

More in Databases