model-writtenrun 7683 - may be wrong, links go to the source messages. Commit-by-commit LLM analysis is in the Commits dialog.
- Masahiko Sawada opened the discussion in #1 around Peter Geoghegan's proposal to remove vacuum_cleanup_index_scale_factor, relying on ANALYZE for index statistics while retaining cleanup scans needed to recycle deleted pages.
- Peter identified VACUUM ANALYZE's incorrect assumption that VACUUM always updates index statistics in #2, then proposed unconditional ANALYZE updates in #3; Tom Lane supported minimizing dependencies between VACUUM and ANALYZE in #4.
- Peter submitted both changes in #5, also marking cleanup-only nbtree tuple counts as estimates, and argued for PostgreSQL 13 backpatches because insert-triggered autovacuum caused unnecessary scans and deduplicated indexes could receive underestimated tuple statistics.
- Masahiko reviewed the patches in #6, requesting a clearer inherited-statistics comment and accepting the nbtree change; Peter incorporated the feedback, reordered the patches, added a WAL version bump, and supplied PostgreSQL 13 versions in #7.
- Peter explained in #7 that PostgreSQL 13 would retain but disable the configuration options, while PostgreSQL 11 and 12 would be left unchanged because users had not reported the related problem there.
- Peter committed the nbtree change as 9f3665fbfc and the VACUUM ANALYZE change as 5f8727f5a6, both from #7 with only comment and commit-message edits, and backpatched both to PostgreSQL 13.
- Peter announced that the work was pushed in #8, and Masahiko acknowledged completion in #9, leaving no patches pending in the thread.