What breaks when you upgrade to PostgreSQL 19?
Two config lines stop the server from starting, one index type stops pg_upgrade, and JIT is now off. Managed clouds still list 18 as the newest version, apart from an Azure preview.

PostgreSQL 19 shipped on November 19, 2026. Three things can block an upgrade: the server will not start if the config still has io_workers or a RADIUS line in pg_hba.conf, pg_upgrade rejects some btree_gist indexes, and JIT is now off. RDS and Cloud SQL do not list version 19 yet.
What stops a PostgreSQL 19 upgrade?
Two configuration lines and one index type. Heise puts them first on its admin checklist. Startup fails when the configuration still has an io_workers entry (io_min_workers and io_max_workers succeed it) or a RADIUS line in pg_hba.conf, since this release drops RADIUS authentication. The pg_upgrade tool refuses to proceed when any inet or cidr column carries a btree_gist index. Dumps made with a pg_dump older than version 19 and with standard_conforming_strings set to off cannot be restored correctly in 19. Search your parameter files and pg_hba.conf for those strings, and ask application owners whether any database still runs with that setting off, before you book a maintenance window.
Which defaults change in PostgreSQL 19?
Two defaults change and one warning is new. Just-in-time compilation is off by default, because the project found its cost estimates for triggering it unreliable, so teams that run many large analytical queries may want to turn it back on. On builds with LZ4 support, TOAST now compresses with lz4 by default. The server also logs a warning after each successful md5 password login, and the md5_password_warnings setting turns it off. Version 18 deprecated md5 and a later release will remove it, so the warning is a prompt to move accounts to SCRAM. Time your heaviest analytical queries on a copy with JIT on and off.
Can you run PostgreSQL 19 on a managed cloud database yet?
Not on the big three yet, apart from one Azure preview. Microsoft's version policy lists PostgreSQL 19 as a preview in East Asia only, with standard support from November 19, 2026 to November 12, 2031. The Amazon RDS release calendar and Google's Cloud SQL page both still show PostgreSQL 18 as the newest version. AWS says a new major version arrives within 30 days of the community's first minor release for it, and Google says within 90 days of general availability. Neither page gives a date for 19 itself, so plan managed upgrades around PostgreSQL 18 for now.
Why did PostgreSQL 19 arrive late, and what was cut?
Heise reports the release landed roughly eight weeks behind the usual schedule, and three weeks behind the plan, because of numerous bug fixes. Release candidate 2 appeared on November 12, alongside updates for versions 14 to 18 that fixed 52 security vulnerabilities, The Register reports. Heise counts between eight and 10 major features dropped during the beta, SQL/PGQ graph queries among them, so check that nothing on your roadmap depended on them. Our earlier story on the delay has the dates and cloud deadlines for PostgreSQL 14.
What should IT teams do about PostgreSQL 19 today?
- Search every config file for io_workers and every pg_hba.conf for RADIUS entries before a test upgrade. The server will not start with either.
- Run
pg_upgrade --checkon a copy of each database to catch inet or cidr columns that carry a btree_gist index. - Confirm standard_conforming_strings is on wherever you will restore dumps made by an older pg_dump.
- Time your heaviest analytical queries with JIT on and off, then decide the default for the new cluster.
- Move any account still on md5 passwords to SCRAM. Our piece on Cloudflare's Basin data platform covers one managed analytics option if you are weighing where data should live.
- Keep managed databases on PostgreSQL 18 until your provider lists 19, and move any PostgreSQL 14 databases first. The project's last 14 release was 14.25.
Sources
- PostgreSQL: PostgreSQL 19 Released!
- heise online: PostgreSQL 19.0, what the new database release brings for developers and admins
- The Register: PostgreSQL patches 52 security holes, sends version 14 into retirement
- Microsoft Learn: Azure Database for PostgreSQL flexible server version policy
- AWS: Release calendars for Amazon RDS for PostgreSQL
- Google Cloud: Cloud SQL for PostgreSQL database versions and version policies