PostgreSQL 19 will be a major release for database administrators. The second beta arrived on 16 July 2026. The stable release is expected in September or October 2026. This version brings long-awaited features such as parallel autovacuum, a built-in REPACK command and online logical replication.
When will PostgreSQL 19 be released?
The first beta landed on 4 June 2026. The second beta followed on 16 July 2026. The team plans the stable release for September or October 2026. Beta builds should not run in production. Still, testing early is a smart way to prepare for the upgrade.
What are the main new features in PostgreSQL 19?
This release includes many changes that affect daily database work. Here are the most talked-about ones:
- Parallel autovacuum: The new
autovacuum_max_parallel_workerssetting spreads index cleanup across several workers. A scoring system now decides which table to clean first. - Built-in REPACK: This command replaces
VACUUM FULLand the pg_repack extension. TheREPACK CONCURRENTLYoption reclaims bloat without locking the table. - Online logical replication: You can turn on replication without a server restart. Sequence replication is now supported too, which stops drift during major upgrades.
- Partition management:
ALTER TABLEgainsMERGE PARTITIONSandSPLIT PARTITION. No more manual detach and attach scripts. - Async I/O:
io_method = workernow scales the worker pool on its own.EXPLAIN ANALYZEalso reports I/O stats.
On the performance side, foreign key checks got faster. This change cuts insert overhead by about %50 on heavy write loads. The LISTEN/NOTIFY system also scales better across many channels.
Read-replica consistency: WAIT FOR LSN
The new WAIT FOR LSN command waits until a read replica reaches the point of your write. This gives you read-your-writes consistency. You no longer need sticky sessions or polling loops.
Which breaking changes should you watch for?
PostgreSQL 19 changes some defaults and removes old features. Review the table below before you upgrade.
| Change | Impact | What to do |
|---|---|---|
| RADIUS auth removed | The server will not start if pg_hba.conf has a RADIUS line | Use LDAP, Kerberos or scram-sha-256 |
| Warning for MD5 passwords | MD5 still works but now emits a warning | Set password_encryption to scram-sha-256 |
| JIT off by default | Analytic queries may run slower | Set jit = on if you need it |
| TOAST compression is lz4 | New and updated rows use lz4 | No action needed; verify lz4 support |
| max_locks_per_transaction is 128 | DDL on partitioned tables fails less often | No action unless you set a custom value |
Moving from MD5 to scram-sha-256 is the most important step in production. Plan the password reset with your users. For server hardening, see our Ubuntu server security guide.
How do you try the PostgreSQL 19 beta?
Do not run the beta against live data. A separate test box is the safest path. Trying it inside a Docker container gets you running in minutes. For a lasting test server, pick a suitable VPS. On the app side, a Django backend lets you test the new release with ease.
Verify the details in the official sources. The announcement is on the PostgreSQL 19 Beta 2 page, and every change is documented in the official release notes.
Frequently asked questions
Can PostgreSQL 19 be used in production?
No. Beta builds are for testing only. Do not move production data until the stable release ships.
Does REPACK make the pg_repack extension obsolete?
Mostly yes. REPACK CONCURRENTLY moves online bloat cleanup into the core. Still, plan for disk space and I/O.
Do I have to change MD5 passwords right away?
Not required, but advised. MD5 still works. Even so, moving to scram-sha-256 is the right security step.