Skip to content
Sandeep Kumar
Databases

PostgreSQL 19 is due on 19 November: check these before you upgrade

PostgreSQL 19 brings REPACK CONCURRENTLY, faster foreign-key checks and parallel autovacuum. It also turns JIT off and doubles a lock default. What to check first.

Plan it

Plan it: No production upgrade on day one. Read the incompatibilities and test 19 against a copy of production before you move.

Sandeep Kumar, Full-stack EngineerSandeep KumarFull-stack Engineer

The PostgreSQL project plans to make version 19 generally available on 19 November 2026, after a second release candidate on 12 November. In its own words, that holds "unless an issue is discovered that requires a delay or an additional release candidate."

There's no reason to upgrade production on day one. There's every reason to read the incompatibilities now, because a few of them change defaults quietly.

The changes worth having

REPACK replaces VACUUM FULL and CLUSTER, which did the same job under confusing names. The big one is REPACK (CONCURRENTLY): it rebuilds a bloated table without the access-exclusive lock, so reads and writes keep working.

Until now that needed the pg_repack extension. Progress shows up in pg_stat_progress_repack.

sql
REPACK (CONCURRENTLY) orders;
  • Foreign-key checks are faster.
  • I/O worker processes now scale automatically.
  • Autovacuum can work on a table's indexes in parallel.
  • A new scoring system decides which tables autovacuum gets to first.

Logical replication can be switched on without a restart when wal_level is replica.

Check these before upgrading

JIT is now off by default. If you run large analytical queries that relied on it, you'll need to switch it back on yourself, and you'd only notice as a slowdown.

The max_locks_per_transaction default goes from 64 to 128, and lock allocation changed, so an existing custom value effectively needs doubling.

io_workers is gone, replaced by io_min_workers, io_max_workers and two timing settings. A config file that still sets it needs editing.

MD5 password authentication now logs a warning after every successful login. That's a nudge to move to SCRAM, and a lot of log noise if you haven't.

Full-text search and pg_trgm now use the database's locale provider for character classification. The notes say to reindex affected indexes and recompute stored tsvector values where behaviour changed. Plan that time into the upgrade.

pg_upgrade refuses clusters with btree_gist indexes on inet or cidr columns, and clusters with line breaks in database, role or tablespace names.

My read

I'd wait for 19.1 for anything that matters, and start testing on 19.0 against a copy of production now. REPACK (CONCURRENTLY) alone is a good reason to plan the move: table bloat is the kind of slow problem that eventually forces a maintenance window.

If you're upgrading the connection layer at the same time, my notes on connection pooling with PgBouncer are worth a read first.

More news