PostgreSQL 18.7: Patch Now, Retire 14, and Test PostgreSQL 19 RC 2

The November PostgreSQL update is more than a routine point release. On November 12, the PostgreSQL Global Development Group shipped 18.7, 17.12, 16.16, 15.20, and 14.25 alongside PostgreSQL 19 Release Candidate 2. The announcement says the update fixes 52 security vulnerabilities and more than 140 bugs.

It also marks the end of PostgreSQL 14. If you operate a production database, there are two separate decisions to make: apply the supported-branch security update, then plan a major-version migration on its own schedule.

PostgreSQL elephant logo

PostgreSQL project logo. Source: PostgreSQL Global Development Group.

What changed in the November update?

The most important security item is CVE-2026-6460. PostgreSQL's advisory describes a type-confusion bug involving ALTER ... SET DATA TYPE and other DDL paths. An object creator could cause the server to execute arbitrary code as the operating-system user running PostgreSQL. The advisory scores it CVSS 8.8.

That does not mean an unauthenticated visitor can simply send one HTTP request and take over a database. The advisory's attack path requires a database user with object-creation capability. It is still a serious privilege-boundary failure, particularly in environments where application roles have more DDL rights than they need.

Another example is CVE-2026-14661, involving dblink and subscriptions appending data to a chosen file. The advisory describes a persistent denial-of-service risk and scores it CVSS 8.1.

The release contains many more fixes. Do not cherry-pick only the two examples above: update to the supported minor version for your major branch.

PostgreSQL 14 has reached end of life

Version 14.25 is the final PostgreSQL 14 update. The project says PostgreSQL 14 will no longer receive security or bug fixes.

That makes the priority different for each installation:

  • PostgreSQL 18, 17, 16, or 15: apply the corresponding November minor update and follow its post-update notes.
  • PostgreSQL 14: apply 14.25 as the final patch, but treat migration to a supported major version as an active project.
  • PostgreSQL 19 RC 2: test it in staging; do not treat a release candidate as a production upgrade target.

The official PostgreSQL 19 release-notes page still carries a placeholder release date, and the official Docker image catalog checked for this run lists 19rc2, not a final 19 image. The planned November 19 GA date should not be treated as confirmation that the final release has shipped.

A small 18.7 test environment

The official PostgreSQL Docker image publishes an exact 18.7 tag. You can use it to test a migration or extension in isolation:

docker run --name pg187-lab \ -e POSTGRES_PASSWORD=localdev \ -p 5432:5432 \ -d postgres:18.7 docker exec -it pg187-lab \ psql -U postgres -c 'SHOW server_version;' 

This is a disposable local lab, not a production deployment. Use a persistent volume and a secret manager for real environments; do not put a real database password in shell history or a committed Compose file.

Before updating a real database, create and verify a backup:

pg_dump -Fc -d "$DATABASE_URL" -f before-18.7.dump pg_restore --list before-18.7.dump 

The custom archive format is useful because pg_restore can inspect and selectively restore it. Store the backup outside the database host and test restoration, not just file creation.

The post-update steps are easy to miss

A minor update from PostgreSQL 18.x to 18.7 does not require a dump and restore. The 18.7 release notes do, however, call out issues that need attention:

  1. Examine the changelog entries that mention REINDEX. Some bugs could cause index corruption, so reindex indexes that may be affected.
  2. If you use PostgreSQL incremental backups, take a new full backup after updating and use it as the base for subsequent incremental backups. The release notes describe multiple ways earlier incremental chains could become corrupt.
  3. Rebuild and validate external extensions against the updated server where their own compatibility or security notes require it.
  4. Run application smoke tests, check replication health, and verify that monitoring and backup jobs still work.

A useful third-party video explains the type-confusion issue behind CVE-2026-6460. It is an explainer, not an official PostgreSQL release video; use the primary advisory for the authoritative affected-version list.

PostgreSQL 19: what is worth testing?

The RC2 documentation describes several changes that deserve staging coverage:

  • REPACK unifies table-repacking work, with REPACK (CONCURRENTLY) designed to reduce blocking while reads and writes continue.
  • Logical replication can replicate sequence values.
  • The new WAIT command supports read-your-writes consistency on standbys.
  • Parallel autovacuum can process table indexes.
  • pg_plan_advice and pg_stash_advice provide new ways to influence planner choices.

The compatibility notes matter just as much. JIT is disabled by default, max_locks_per_transaction defaults to 128 rather than 64, and standard_conforming_strings is always on. RADIUS support is removed. The release notes also recommend reindexing full-text-search and pg_trgm indexes after certain pg_upgrade paths, and recomputing stored tsvector values.

Do not build a migration plan from an early beta blog post. Features can be removed or changed during the release cycle. Use the current RC2 release notes as the source of truth and test your extensions, collation behavior, SQL, replication, and backup tooling.

Choosing an upgrade path

A minor update and a major upgrade are not the same operation.

Situation Typical path
18.6 to 18.7 Package or container update, restart, then follow the 18.7 post-update notes
14 to 18 Plan a major upgrade using pg_upgrade, dump/restore, or logical replication
18 to 19 RC 2 Isolated staging test only until the final release is officially announced

For a major upgrade, pg_upgrade --check can validate cluster compatibility before changing data. Its general shape is:

pg_upgrade --check \ -b /path/to/old/bin -B /path/to/new/bin \ -d /path/to/old/data -D /path/to/new/data 

The paths are installation-specific. Install compatible extension binaries for the target server, check collation and locale behavior, and read the official upgrade guide before running the actual migration. pg_upgrade is not needed for a minor-version update.

The practical decision

If you are already on a supported branch, apply its November security update and complete the release-specific reindex and backup checks. If you are still on PostgreSQL 14, do not stop at 14.25: it is the final patch, not a new support window. If you want PostgreSQL 19 features, run RC2 against representative workloads and wait for the project's final release announcement before planning production rollout.

Sources and further reading

Which PostgreSQL branch are you running today, and have you tested a restore from your latest backup?

Written by Shaswat Raj

GitHub · LinkedIn · YouTube: StackShade