The report
Peter Eisentraut's October 9 account describes roughly eight to ten PostgreSQL 19 feature reversions, compared with about one in a typical cycle. He identifies several pressures, including concentrated LLM-assisted bug discovery, architectural problems and earlier security workload. His account says reversion was chosen to preserve the schedule.
The later official October 15 release announcement plans RC2 for November 12 and general availability for November 19 to incorporate additional fixes. It does not attribute that decision solely to AI. A claim that AI alone delayed PostgreSQL therefore combines observations that the sources support separately.
The connection to AI-assisted repair is operational: finding more defects can increase the load on diagnosis, patch review and regression verification. The separately documented Trail of Bits patch review provides a concrete comparison, without establishing that PostgreSQL experienced the same regression rate.