The PostgreSQL 19 release date has moved. The final version is now planned for November 19, 2026, a week later than the original plan, and you get an extra release candidate on the way.
If you run Postgres in production, nothing breaks today. You just have a bit longer to test before you upgrade.
Here are the quick facts before the details.
- RC1 shipped on October 15, 2026, as planned.
- A new RC2 is set for November 12, 2026.
- General availability (GA) is now November 19, 2026, unless a problem forces another delay.
- Reports say several big features were pulled and pushed to PostgreSQL 20.
The short version: the dates are firm for now, but the release team says it will slip again if it has to.
What changed with the PostgreSQL 19 release date
On October 10, Jonathan S. Katz posted an updated schedule to the pgsql-hackers list on behalf of the release team. RC1 stayed on October 15. RC2 is new, and GA moved to November 19.
The reason is simple. A lot of fixes piled up in the back branches, and the team wanted testers to get them before the final build. RC2 lands on the same day as the scheduled minor update release, and GA follows one week later.
Katz also called this an atypical major release cycle and said the team wants the release to be stable and reliable.
Why this cycle ran into trouble
The official note doesn’t blame any one cause. The Register adds more color, citing a blog post by Peter Eisentraut, a PostgreSQL committer at EDB. He said LLM-assisted code review found serious flaws in some features and many small edge-case bugs.
Eisentraut also said the quality bar rose after those features were committed. He denied that “vibe coding” caused the reverts, since that technique wasn’t around when most of the code was written.
That’s one account, so treat it as context rather than the official cause. If AI review is catching bugs earlier, you may see more cycles like this one. We covered a related tool in our post on GitHub Agentic Autofix.
What was cut and what stayed in PostgreSQL 19
The Register reports that between eight and 10 significant features were dropped and will likely land in PostgreSQL 20. The table below shows the ones named in the sources.
| Feature | Status in v19 | Source |
|---|---|---|
| SQL property graph queries (SQL/PGQ) | Pulled, moved to a later release | The Register |
| REPACK (CONCURRENTLY) | Kept, with several RC1 fixes | RC1 notes |
| Parallel autovacuum | Kept, with several RC1 fixes | RC1 notes |
| pg_plan_advice | Kept, with several RC1 fixes | RC1 notes |
REPACK CONCURRENTLY is the one many admins care about. It reclaims disk space without the long table lock that VACUUM FULL takes.
What the RC1 fixes tell you
The RC1 notes list the bugs fixed since Beta 4. They show where the late-stage risk sat.
- Several fixes for REPACK (CONCURRENTLY), parallel autovacuum, and pg_plan_advice.
- Fixes for planner optimizations that depend on whether an expression can be NULL.
- A postgres_fdw fix so statistics import runs as the foreign table’s owner, not the user running ANALYZE.
- A fix so COPY (query) TO with JSON format uses the query’s column names, including aliases, as keys.
If you use logical replication, the notes also mention a fix for automatic enablement when wal_level is replica. Check that one if you plan to test replication.
Planner and replication fixes are the ones that can change query behavior quietly. That’s why a longer test window helps. For another look at AI-written code in real software, see how Claude Code wrote a Linux driver.
What to do before you upgrade
Don’t plan a production move to a .0 release the week it lands. Use the extra weeks to test.
- Spin up RC1 in a test environment and run your real queries against it.
- Rehearse the upgrade with
pg_upgrade --checkor a dump and restore, as the RC1 announcement describes. - Re-test after RC2 on November 12, since it carries many of the late fixes.
Doing this now means a bad surprise shows up in staging, not in production.
Frequently Asked Questions
When is the PostgreSQL 19 release date?
The planned date is November 19, 2026. The team says it could move again if a serious problem turns up.
Is PostgreSQL 19 safe to use right now?
RC1 is a release candidate, so it’s meant for testing. Use it in staging, not production.
Did PostgreSQL 19 lose features?
According to The Register, yes. SQL property graph queries were pulled, and several others were pushed to PostgreSQL 20.
Do I need to upgrade from PostgreSQL 18 right away?
No. Your current version keeps getting its normal updates. Wait for the final release and test first.
Should you wait for PostgreSQL 19?
Yes, wait. A one-week slip and an extra release candidate is a healthy sign, not a red flag. Test RC1 now, retest on RC2, and plan your real upgrade for a few weeks after November 19.
Leave a Reply