The reverts will continue until morale improves(peter.eisentraut.org)
231 points by hans_castorp 6 days ago | 46 comments
tl;dr: PostgreSQL 19's beta saw an unusually high number of feature reverts (8-10), largely because LLM-assisted code review and fuzzing surfaced many edge-case defects that previously would have trickled in over years, effectively raising the quality bar faster than older in-progress features could meet. Compounding this, senior developers were tied up with security work ("Vulnpocalypse"), leaving less time for beta review and fixes before the release deadline. The author suggests the community should invest in more robust internal interfaces and a mechanism for landing features as "experimental" to mature in-tree.
HN Discussion:
  • ↑Reverting is the right call for a foundational project like Postgres to maintain quality and community trust
  • ↑LLM-assisted review legitimately surfaces edge cases that would have taken years to find, validating the author's explanation
  • ↑Projects should consider feature freezes to adapt to the new LLM-driven quality bar
  • ↓Self-imposed OSS deadlines shouldn't force reverts; just delay the release instead
  • ↓The article is clickbait-titled and buries its actual point about LLMs