PostgreSQL 19 Slips to October: Beta 4 Is Out and Several Features Were Pulled
PostgreSQL 19 missed its usual September release. Beta 4 shipped on 24 September 2026, with a release candidate planned for early October and GA possibly in October. SQL/PGQ graph queries, online checksum switching, FOR PORTION OF and partition MERGE/SPLIT were removed. What's still in 19, and whether to wait.
PostgreSQL major versions usually ship in September. PostgreSQL 19 didn't. The project released Beta 4 on 24 September 2026, with a release candidate planned for early October and general availability that "may also occur in October", depending on testing.
Features pulled from 19
To protect reliability and the schedule, the community removed several features during the beta. They may return in a later release:
- SQL/PGQ — property graph queries.
- Online enabling and disabling of data checksums.
- Temporal
UPDATE/DELETEwithFOR PORTION OF. ALTER TABLE ... MERGE PARTITIONS/SPLIT PARTITIONS.pg_get_role_ddl(),pg_get_tablespace_ddl()andpg_get_database_ddl().
If you'd read a "what's new in Postgres 19" article earlier in the year, double-check anything you were planning around.
What's still in
Beta 4's notes mention fixes to these 19 features, which remain:
REPACK— rebuild bloated tables (and indexes) in core, in the territory long served byVACUUM FULLand thepg_repackextension. (Postgres REINDEX CONCURRENTLY and Index Bloat)WAIT FOR.CREATE PUBLICATION ... EXCEPT— publish everything except certain tables. (Postgres Logical Replication)- Logical replication conflict detection, and initial table sync from older versions.
- A new autovacuum scoring system to prioritise which tables to vacuum. (Postgres VACUUM and Bloat)
pg_plan_advicefor influencing query plans.- Faster foreign-key checks and SIMD-optimised
COPY FROM. (Import a CSV Into Postgres)
Should you wait for 19?
No — PostgreSQL 18 is the right production choice today. It brought asynchronous I/O, uuidv7(), virtual generated columns and more, and it has a year of patch releases behind it. (UUIDv7 Explained, Postgres Generated Columns)
When 19 reaches GA, the usual advice applies: test your application and extensions against it, wait for the first minor release or two for production, and upgrade with pg_upgrade or logical replication. (Postgres Major Version Upgrade)
If you want to help, test the betas and release candidates against a copy of your workload — that's exactly what the extra beta time is for.
Source: PostgreSQL 19 Beta 4 announcement · PostgreSQL roadmap
EasySpawn runs a current, stable PostgreSQL next to your app on every server, with daily backups — and Claude Code to help you test new versions on a copy first. See how it works or join the waitlist.
Related: What Is PostgreSQL? · Postgres vs MySQL · Postgres Transaction ID Wraparound · Postgres Backup and Restore
Keep reading
Supabase Is Acquiring Turso to Build Database Infrastructure for AI Agents
Supabase announced on 2 October 2026 that it is acquiring Turso, the company that rebuilt SQLite in Rust and runs a platform for millions of on-demand databases. Turso keeps operating, Supabase stays Postgres-first, and nothing changes for existing users. Why agent-created databases are driving the deal and what to watch.
Replit Adds Scheduled Daily Backups for Production Databases
On 4 September 2026 Replit added scheduled backups for production databases: one full restore point per day, kept for a retention period you choose (limits depend on plan), alongside a new Project Analytics pane. What it covers, what it doesn't, and the backup checklist every Replit app should still follow.