The reverts will continue until morale improves

PostgreSQL 19’s development branch has reverted roughly eight to 10 significant features after its beta period began, far above the roughly one revert per release cycle that may be expected. Some reversions occurred late in beta. PostgreSQL developer Peter Eisentraut said the affected code may in some cases have been insufficient, while other features proved too difficult to complete on schedule or had architectural defects that could not be fixed quickly. Eisentraut said LLM-assisted code review and fuzzing can uncover edge cases much faster than earlier testing methods, producing large volumes of defect reports for features written before those tools became as useful. He also linked late discoveries to senior developers’ security-fix work during the ongoing “Vulnpocalypse” from April through the August PostgreSQL security release, which reduced normal beta-period review and testing. He said PostgreSQL’s broad feature interactions make exhaustive manual testing impractical and argued that LLM-assisted fuzzing should become part of feature development, alongside more robust internal interfaces. The community chose to preserve the release schedule rather than delay PostgreSQL 19 for additional fixes. Eisentraut expects many reverted features to return, while PostgreSQL 19 will retain features including REPACK CONCURRENTLY, logical replication of sequences, and planner hinting through pg_plan_advice.