"PostgreSQL 19 New Features App Developers Should Know"
PostgreSQL 19 new features for app developers: ON CONFLICT DO SELECT, REPACK CONCURRENTLY, WAIT FOR LSN, plus what beta 4 cut — and the release timeline.
The postgresql 19 new features list looks different than it did two months ago. Beta 4 (shipped 2026-09-24) pulled several headline features — SQL/PGQ graph queries, GROUP BY ALL , temporal tables — back out of the release. What's left is a smaller, more operational release: atomic get-or-create with ON CONFLICT DO SELECT , online bloat removal with REPACK , read-your-writes on replicas with WAIT FOR LSN , parallel autovacuum, and a planner that can give you advice. Here's what matters if you build apps on Postgres, what's gone, and when you can actually use any of it. BETA FLAG: PostgreSQL 19 is still beta as of this writing (beta4: 2026-09-24; RC1 scheduled 2026-10-15; GA scheduled 2026-10-29). PostgreSQL 18.x is the current GA release. Nothing below is production advice — test on 19 beta, ship on 18. Last updated: October 4, 2026 What you'll learn The PG19 timeline: beta4 → RC1 (Oct 15) → GA (Oct 29, 2026) Which features were cut in beta4 (SQL/PGQ, GROUP BY ALL, temporal tables, and more) The five features still shipping that affect app backends: ON CONFLICT DO SELECT, REPACK, WAIT FOR LSN, parallel autovacuum, pg_plan_advice New defaults you need to know about (JIT off) Whether you should upgrade, and what to test now PostgreSQL 19 Release Date and Status First, the timeline — because half the confusion around PG19 is people testing beta behavior as if it were final: Beta 4 shipped 2026-09-24. This is the current build. RC1 is scheduled for 2026-10-15 . GA is scheduled for 2026-10-29 . That's per the mailing-list announcement of the release schedule. No GA announcement exists as of October 4, 2026, so if someone tells you PG19 is out, they're wrong or time-traveling. Is PostgreSQL 19 production-ready? No. Betas exist so the community…