Recommended Free Tools
PostgreSQL 19 is still planned for release, but its schedule has moved: the project plans a second release candidate on November 12, 2026, and general availability on November 19, unless another issue forces a change. The delay reflects late defect discovery, feature reversions, and an unusually heavy security workload—not evidence that AI alone broke the release or that human maintainers cannot fix the bugs.
What changed in the PostgreSQL 19 schedule
The previous general-availability target was October 29, announced on September 28. PostgreSQL’s latest plan, published October 15, calls for RC2 on November 12 and GA on November 19. Both dates remain conditional: another release-blocking issue could move them again.
As an Amazon Associate I earn from qualifying purchases.
| Milestone | Date or status | What it means |
|---|---|---|
| Previous GA target | October 29, 2026 | The date announced on September 28 and subsequently missed |
| Release candidate 2 | November 12, 2026 | Planned stabilization build, subject to unresolved issues |
| General availability | November 19, 2026 | Current target, unless another problem requires a delay |
That makes PostgreSQL 19 an upcoming release rather than a canceled one. Release candidates are intended for compatibility testing and bug reports, not production deployment.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteWhy the release was delayed
Several pressures arrived together late in the cycle. Maintainers removed or reverted features that were not ready for the reliability standard expected of a major PostgreSQL release. AI-assisted reviews also surfaced additional defects and edge cases after the feature freeze, increasing the amount of code that needed human analysis. At the same time, maintainers were handling a large security-fix workload.
#1 Best Overall
These factors are related but not interchangeable. The available evidence supports AI as an accelerator of discovery and review workload. It does not establish that AI was the sole cause of the schedule change, nor that humans were unable to repair the reported defects.
Did AI reviewers find more bugs than humans can fix?
Percona contributor Zsolt Parragi reports that several PostgreSQL 19 issues were found during AI reviews and says recent model improvements arrived after the feature freeze. His assessment is that current models can find “as many issues in a patch as humans do, or more.” That is an expert observation, not a controlled comparison of every human and AI finding in PostgreSQL 19.
No cited source provides a complete count of AI-discovered versus human-discovered bugs, model accuracy, or false-positive rates. AI reviews can elevate minor issues or generate noise, so maintainers still decide whether a finding is valid, how severe it is, whether a patch needs redesign, and whether a feature should be reverted. Parragi’s recommended division of labor is for models to broaden review coverage while humans handle design questions and filter findings that do not justify blocking a release.
Features PostgreSQL 19 reverted or removed
Beta 4 explicitly backed out several changes. Reverting them reduces the amount of new behavior that must be stabilized before GA and leaves the project free to revisit the work in a later cycle.
| Feature or change | Beta 4 action |
|---|---|
| SQL/PGQ property-graph support | Reverted |
| Online enabling and disabling of data checksums | Reverted |
Temporal updates and deletes using FOR PORTION OF |
Reverted |
ALTER TABLE ... MERGE PARTITIONS and SPLIT PARTITIONS |
Reverted |
| Several DDL helper functions | Removed |
Beta 4 also listed fixes for REPACK, WAIT FOR, logical replication, autovacuum scoring, COPY SIMD behavior, and crashes while detaching partitions.
What RC1 fixed after Beta 4
The RC1 announcement recorded another group of corrections:
- REPACK with
CONCURRENTLY pg_plan_advice- Planner optimizations involving nullable expressions
- Automatic enablement of logical replication
- Statistics ownership in
postgres_fdw - Parallel autovacuum
- JSON-key handling for
COPY (query) TO ... (FORMAT json)
The continued stream of fixes is normal for a release candidate, but it explains why the project is preserving additional review time instead of treating the missed October target as a reason to ship immediately.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →How much did security work contribute?
Parragi’s Percona analysis reports a sharp increase in security fixes during 2026. The figures are his charted totals, not an independently audited PostgreSQL security database.
Best Value
| Year | Security fixes reported by Parragi |
|---|---|
| 2020 | 7 |
| 2021 | 8 |
| 2022 | 2 |
| 2023 | 8 |
| 2024 | 7 |
| 2025 | 7 |
| 2026 so far | 44 |
He reports that 28 of the 44 fixes arrived in August, during the beta period. Security response competes for the same experienced committer and reviewer time needed to evaluate release-candidate regressions, so the workload adds schedule pressure even when the security issues are not caused by PostgreSQL 19’s new features.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Can you test PostgreSQL 19 now?
Yes. Release candidates are specifically available for evaluation, and user testing is part of the stabilization process. Treat every RC as pre-GA software and test it against a disposable copy of your own databases and workloads.
Quick Recap
- Use a non-production environment. Restore a representative database, application schema, extensions, backup jobs, monitoring rules, and migration scripts.
- Choose a major-version upgrade path. The official RC guidance points to
pg_upgradeor a logical dump-and-restore withpg_dumpandpg_restore. Plan storage, downtime, rollback, and extension compatibility before changing a test cluster. - Exercise real workloads. Run query plans, partition maintenance, replication, autovacuum, COPY pipelines, failover procedures, and backup restores rather than relying only on a clean installation.
- Report reproducible problems. Include the exact RC build, operating system, SQL or configuration needed to reproduce the issue, logs, and whether the behavior differs from PostgreSQL 18.
- Wait for GA before production adoption. Re-run the same checks against the final build after the release candidate period, even if an RC performs well.
What PostgreSQL users should expect next
- The immediate milestone is RC2 on November 12, 2026.
- GA is planned for November 19, 2026, but remains contingent on release quality.
- Features reverted from Beta 4 should not be treated as PostgreSQL 19 capabilities; they may return in a later major version after further design and testing.
- The delay demonstrates a conservative release policy: maintainers would rather remove unstable functionality and investigate late findings than ship a major version with known uncertainty.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
