iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
PostgreSQL 19 is still coming. The project’s latest schedule, published October 15, 2026, plans a second release candidate (RC2) for November 12 and general availability (GA) for November 19, unless another release-blocking issue appears. The delay is the result of late defect discovery, feature reversions, and an unusually heavy security workload—not evidence that AI reviewers made the release impossible to finish.
When will PostgreSQL 19 be released?
The October 15, 2026 plan moves PostgreSQL 19’s expected GA date to November 19, with RC2 scheduled for November 12. That is a change from the October 29 GA target announced on September 28. Both dates remain conditional: another serious problem could require more stabilization work.
| Milestone | Plan or status |
|---|---|
| Earlier GA target | October 29, 2026, announced September 28 |
| Current RC2 target | November 12, 2026 |
| Current GA target | November 19, 2026, subject to no further release-blocking issue |
That makes PostgreSQL 19 a delayed release, not a canceled one. Release candidates are pre-GA builds intended to expose remaining problems before production adoption.
Why the schedule moved
Several pressures converged late in the cycle. Maintainers removed or reverted features that were not stable enough for the release, increasingly capable AI-assisted reviews produced more findings, and a large security-fix workload consumed committer time. Treating any one of those factors as the sole cause would overstate what the available evidence shows.
#1 Best Overall
Reliability decisions took priority over feature count
PostgreSQL 19 Beta 4 reverted SQL/PGQ property-graph support, online enabling and disabling of data checksums, temporal updates and deletes using FOR PORTION OF, and ALTER TABLE ... MERGE PARTITIONS and SPLIT PARTITIONS. Several DDL helper functions were also removed.
Those changes reduce the feature surface that must be supported and reviewed for the first PostgreSQL 19 release. A feature being reverted does not necessarily mean it will never return; it means it was not considered ready for this version’s reliability bar.
Defect fixing continued after Beta 4
The Beta 4 cycle listed fixes involving REPACK, WAIT FOR, logical replication, autovacuum scoring, COPY SIMD, and partition-detach crashes. The RC1 announcement then recorded additional work on REPACK with CONCURRENTLY, pg_plan_advice, nullable-expression planner optimizations, automatic logical-replication enablement, postgres_fdw statistics ownership, parallel autovacuum, and JSON key handling for COPY (query) TO ... (FORMAT json).
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →The breadth of that list explains why maintainers chose more review time instead of holding to the earlier calendar date.
Did AI reviewers break the PostgreSQL 19 release?
No. The evidence supports a narrower explanation: better AI review increased the volume and complexity of issues discovered late in the cycle, adding work for human maintainers. It does not show that AI alone caused the delay, that AI-generated findings were all valid, or that humans were unable to fix them.
Percona contributor Zsolt Parragi reported that several issues were found through AI reviews and that major model improvements arrived after PostgreSQL 19’s feature freeze. His assessment was that “the current models already find as many issues in a patch as humans do, or more.” He also argued that models can improve future contributions when humans handle design questions and filter out minor or noisy findings that might otherwise be treated as blockers.
No controlled count in the cited material compares AI-found with human-found PostgreSQL 19 bugs, and there is no measured accuracy or false-positive rate. The defensible conclusion is that AI acted as an accelerant for discovery and review workload while people retained responsibility for severity judgments, design decisions, reverts, and release timing.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
How large was the security workload?
Parragi’s Percona analysis reports a sharp increase in security fixes during 2026. These figures are his analysis, not an independently audited PostgreSQL security database.
| Year | Security fixes reported by Parragi |
|---|---|
| 2020 | 7 |
| 2021 | 8 |
| 2022 | 2 |
| 2023 | 8 |
| 2024 | 7 |
| 2025 | 7 |
| 2026 so far | 44, including 28 in August |
The 44 figure covers 2026 to the point of Parragi’s analysis rather than a completed calendar year. The concentration of 28 fixes in August, during the beta period, helps explain why security work competed with release stabilization for limited committer attention.
What changed in PostgreSQL 19 compared with the planned feature set?
The most visible change is that several ambitious capabilities will not ship in PostgreSQL 19 as previously planned:
- SQL/PGQ property-graph support
- Online enabling and disabling of data checksums
- Temporal updates and deletes using
FOR PORTION OF ALTER TABLE ... MERGE PARTITIONSALTER TABLE ... SPLIT PARTITIONS- Several DDL helper functions
Removing these items is a deliberate reliability trade-off. PostgreSQL users get a smaller, more thoroughly reviewed release rather than retaining features that could create upgrade, planner, replication, or crash risks.
Can you test PostgreSQL 19 now?
Yes. Beta and release-candidate builds are available for evaluation, and user feedback is part of the stabilization process. They should be treated as pre-GA software, not as drop-in production upgrades.
Best Value
- Use a non-production environment. Restore a representative copy of your databases and run the queries, extensions, replication jobs, backup tasks, and maintenance routines that matter to your workload.
- Choose a major-version upgrade method. The official RC1 guidance points to
pg_upgradeor a logical dump-and-restore sequence usingpg_dumpandpg_restore. Plan for the storage, downtime, compatibility checks, and rollback path required by your chosen method. - Exercise changed areas. Pay particular attention to partition operations, logical replication, autovacuum behavior, COPY paths, foreign-data wrappers, planner output, and any extension that interacts with features fixed in RC1.
- Report reproducible problems. Include the PostgreSQL build, operating system, schema or test case, SQL statements, expected result, actual result, and logs when reporting an issue to the PostgreSQL project.
- Wait for GA for normal production decisions. Re-test the final release candidate and verify extension and operational-tool support before scheduling a production migration.
A major-version upgrade still requires a migration strategy even when the server is stable. Test restoration and rollback, not only the new server’s startup.
What the delay means for PostgreSQL users
For users, the practical result is a later target date and a narrower feature set, offset by additional time for review. Existing PostgreSQL deployments do not need an emergency response simply because PostgreSQL 19 moved. Teams planning an upgrade should update project schedules, continue testing candidate builds, and avoid treating the November 19 date as guaranteed until the project declares GA.
The headline claim that AI reviewers found “more bugs than humans can fix” is therefore misleading. AI helped surface more work at a sensitive point in the release, but human maintainers are still deciding what matters, changing the code, reverting risky features, and determining when PostgreSQL 19 is ready.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallQuick Recap
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.
