PostgreSQL 19 is the next major release of the open-source database, with general availability planned for November 19, 2026. It adds a new REPACK command, tools for steering the query planner, faster foreign key checks and easier logical replication. It also changes a few defaults that app teams will notice.
This post is based on the PostgreSQL 19 release candidate. Everything here is as of RC 1, released October 15, 2026, and the release notes, which are dated as of October 9, 2026. The project says a release candidate "will be mostly identical" to the final release, but some fixes may still land. Our PostgreSQL 14 end of life guide covers the deadline that pushed many teams to plan an upgrade this year. This post answers the next question: should that upgrade go to 18 or to PostgreSQL 19?
The short version: most teams should move to PostgreSQL 18 now and plan PostgreSQL 19 after its first minor releases. Managed providers add new major versions weeks to months after the community release. Extensions and drivers need time too. Version 19 makes sense early for new self-hosted projects and for teams that need REPACK without locking tables.
What PostgreSQL 19 adds
The PostgreSQL 19 release notes list these headline changes in their overview:
| Feature | What it does | Who will notice |
|---|---|---|
| REPACK | Reclaims disk space and reorganizes a table. REPACK (CONCURRENTLY) does it without blocking reads and writes. | Anyone with large, bloated tables |
| pg_plan_advice and pg_stash_advice | Extensions that steer query planner decisions, and apply that advice automatically per query | Teams fighting one slow query plan |
| Performance work | Automatic scaling of I/O worker processes, quicker foreign key checks, more planner and executor gains | Most workloads, without changes |
| Logical replication without a restart | Can be turned on when wal_level is set to replica | Teams planning low-downtime moves |
| Sequence replication | Logical replication now copies sequence values | Anyone migrating with logical replication |
| WAIT command | Lets a standby wait until it has caught up, for “read-your-writes” reads | Apps that read from replicas |
| Parallel autovacuum | Vacuums a table’s indexes in parallel and ranks tables by need | Busy databases with many indexes |
REPACK is the change most teams will feel first. The release notes say it "replaces VACUUM FULL and CLUSTER." The old commands remain for compatibility. VACUUM FULL locks a table while it runs, so it is hard to use on a live site. The CONCURRENTLY option removes that lock.
Sequence replication matters for upgrades. Before PostgreSQL 19, logical replication did not copy sequence values, so teams had to sync them at the cutover.
Smaller PostgreSQL 19 changes for developers
Further down, the release notes list changes that app developers may use soon:
- COPY TO can write JSON. A FORCE_ARRAY option wraps the output in a single JSON array.
- INSERT … ON CONFLICT DO SELECT … RETURNING. An insert that hits a conflict can return the existing row.
- IGNORE NULLS and RESPECT NULLS for window functions.
- More jsonpath string methods, such as lower(), upper(), replace() and split_part().
- Casts between bytea and uuid.
- Server-side SNI for TLS, set up in a new pg_hosts.conf file.
Some defaults change too. TOAST compression now defaults to lz4 instead of pglz, and log_lock_waits is on by default.
PostgreSQL 19 changes that can break app and CMS code
The "Migration to Version 19" section lists 17 changes that may affect compatibility. These are the ones most likely to reach a CMS or web app:
| Change | What breaks | What to do |
|---|---|---|
| standard_conforming_strings always on | Dumps from older pg_dump made with the setting off will not load properly | Dump with the version 19 pg_dump |
| JIT off by default | Large reporting queries may run slower | Turn JIT on for analytics workloads |
| max_locks_per_transaction default 64 to 128 | Lock sizing changed, so old custom values give about half the capacity | Double any custom value |
| Warning after MD5 password login | Extra warnings in logs and clients | Move roles to SCRAM passwords |
| RADIUS removed | RADIUS logins stop working | Switch authentication methods first |
| json_array() with no rows | Returns an empty array instead of NULL | Check code that tests for NULL |
One more is worth a look. Transactions marked READ ONLY now pass that status to postgres_fdw sessions, so they can no longer change rows on a remote server.
The MD5 change continues a path that started in PostgreSQL 18. Version 18 marked MD5 passwords deprecated and said support "will be removed in a future major version release." Version 19 adds a warning at login.
What blocks a PostgreSQL 19 upgrade
Some changes stop pg_upgrade outright. The release notes say pg_upgrade "will refuse to upgrade" in these cases:
- Database, role or tablespace names with carriage returns or line feeds. These are now disallowed for security reasons.
- btree_gist indexes on inet or cidr columns. The release notes say these are broken because they “can exclude rows that should be returned.” The default now uses GiST instead.
Databases using the rarely used MULE_INTERNAL encoding must be dumped and restored with a different encoding.
Run pg_upgrade --check against a copy before anything else. The pg_upgrade documentation says check mode changes no data and "will also outline any manual adjustments you will need to make."
Upgrade paths to PostgreSQL 19 from 14 through 18
Every major upgrade needs one of three methods: dump and restore, pg_upgrade, or logical replication. The pg_upgrade documentation for version 19 says it supports upgrades "from 9.2.X and later," so any version from 14 to 18 can go straight to 19.
You can skip versions. The upgrade guide says you should still "read the major release notes of all intervening versions." Here is what to look for on each path:
| Starting version | Community support ends | Migration notes to read |
|---|---|---|
| 14 | November 12, 2026 | 15, 16, 17, 18 and 19 |
| 15 | November 11, 2027 | 16, 17, 18 and 19 |
| 16 | November 9, 2028 | 17, 18 and 19 |
| 17 | November 8, 2029 | 18 and 19 |
| 18 | November 14, 2030 | 19 only |
Support dates come from the PostgreSQL versioning policy. Three older changes catch teams coming from 14 to 17:
- Version 15 removed the default CREATE permission on the public schema. Upgrades keep the old permissions. New databases do not get them, so an app user that does not own the database cannot create tables there.
- Version 17 runs maintenance commands with a safe search_path. Functions behind expression indexes that reference other schemas must set their own search path.
- Version 18 turned on data checksums by default in initdb. pg_upgrade needs matching checksum settings, so an old cluster without checksums needs the new cluster created with –no-data-checksums.
Since version 18, pg_upgrade also carries most optimizer statistics over, so the new server plans queries well sooner. For dumps, the docs recommend using pg_dump from the newer version. With PostgreSQL 19 that matters more because of the standard_conforming_strings change. Take a tested backup first, as covered in our backup strategy basics.
When managed providers add PostgreSQL 19
Providers set their own timing. Here is what each one publishes, as of October 21, 2026:
| Provider | Published timing for new majors | PostgreSQL 19 status |
|---|---|---|
| AWS RDS for PostgreSQL | Within 30 days of the community release of the first minor version (19.1) | Beta builds offered in the RDS Database Preview Environment |
| Google Cloud SQL | Within 90 days of general availability | Not listed; 18 is the default |
| Azure Database for PostgreSQL | No timeline published | Not listed; 18 is listed |
| Heroku Postgres | After testing for compatibility, no date | Not listed; 18 is the default |
| Render | No timeline published | Listed as not yet supported |
| Supabase | No timeline published | Not mentioned in upgrade docs |
Sources are the RDS release calendar, Google’s Cloud SQL version page and each provider’s own version docs.
For a sense of the gap, RDS added PostgreSQL 18 on November 14, 2025. The community released 18 on September 25, 2025. AWS’s preview environment is for testing: its July announcement says preview instances are kept for at most 60 days.
Heroku’s support page adds one more detail. It says "Heroku Postgres 16 deprecates when Heroku Postgres 19 releases." Teams on Heroku 16 should watch for that.
Supabase users can read our Supabase explainer for how its managed Postgres works.
Drupal and PostgreSQL 19
Drupal’s database server requirements list PostgreSQL 16 or later for Drupal 11 and 18 or later for Drupal 12. The page does not mention version 19 as of October 2026. A Drupal site on 18 meets both requirements and has support until November 2030.
Our recommendation: 18 now, PostgreSQL 19 later
For most teams, PostgreSQL 18 is the right target today. AWS, Google, Azure, Heroku and Render all offer it. Drupal 12 requires it. It is supported until November 14, 2030.
Plan PostgreSQL 19 for after its first minor releases. PostgreSQL’s roadmap lists the next scheduled update releases as February 11 and May 13, 2027. Each one brings a new minor release for every supported version. By then, your provider may have added 19, and the extensions you rely on will have had time to catch up. That includes tools like pgvector, which we covered in our pgvector on Supabase guide.
Going to PostgreSQL 19 early makes sense in a few cases:
- A new, self-hosted project with no legacy data.
- Large tables where REPACK (CONCURRENTLY) would avoid a long lock.
- A planned logical replication cutover that would benefit from sequence replication.
Before any move, test on a copy. Run pg_upgrade in check mode, review custom lock and JIT settings, and confirm every extension has a build for 19. Teams letting AI agents work against a database, as in our Supabase MCP server post, should point those agents at the test copy only.
Frequently Asked Questions
When is PostgreSQL 19 released?
General availability is planned for November 19, 2026, according to the RC 1 announcement. A second release candidate was planned for November 12, alongside the regular update release.
What is the biggest new feature in PostgreSQL 19?
For most teams, the REPACK command. It reclaims disk space like VACUUM FULL, and its CONCURRENTLY option does it without blocking reads and writes.
Should I upgrade to PostgreSQL 19 right away?
Most teams should not. Move to 18 now and plan 19 after its first minor releases, once your provider and extensions support it.
Can I upgrade from PostgreSQL 14 straight to 19?
Yes. pg_upgrade supports upgrades from 9.2 and later. Read the migration notes for every version in between, from 15 through 19.
Will my old pg_dump backups restore into PostgreSQL 19?
Possibly not. Dumps made by older pg_dump with standard_conforming_strings set to off will not load properly. Use the version 19 pg_dump for the move.
Why are my reporting queries slower on PostgreSQL 19?
JIT compilation is now off by default. Sites that run many large analytical queries need to turn it back on.
When will AWS RDS offer PostgreSQL 19?
AWS says within 30 days of the community release of the first minor version, 19.1. Beta builds have been available in its preview environment for testing.
Does Drupal support PostgreSQL 19?
Drupal’s requirements page does not mention 19 as of October 2026. Drupal 12 requires PostgreSQL 18 or later.
Does PostgreSQL 19 still support MD5 passwords?
Yes, but it now warns after each successful MD5 login. MD5 was deprecated in PostgreSQL 18 and is set to be removed in a future major version.