model-writtenrun 8739 - may be wrong, links go to the source messages. Commit-by-commit LLM analysis is in the Commits dialog.
- Daniel Gustafsson proposed removing automatic conversion of pre-7.3 foreign-key triggers because the SQL-reachable code lacked tests and likely saw little use, initially targeting PostgreSQL 14 in #1.
- Alvaro Herrera argued that PostgreSQL 13 was appropriate because pg_dump had already dropped pre-8.0 servers and older databases could upgrade through an intermediate version; Tom Lane supported the cleanup alongside his OPAQUE-removal proposal, and Daniel accepted the earlier target in #2, #3, and #5.
- Tom Lane expanded the discussion to obsolete operator-class names silently replaced by defaults in CREATE INDEX, arguing that this could interfere with new operator classes, and also raised the separate rtree-to-gist fallback in #6.
- Alvaro Herrera supported removing the operator-class workaround but favored retaining the harmless, regression-tested rtree fallback in #8.
- Tom Lane committed Daniel's original foreign-key patch from #1 as e58a599752, additionally deleting an obsolete comment, and independently implemented his inline operator-class proposal from #6 as 84eca14bc4 with a nearby comment correction.
- Shortly after both commits, Daniel posted the unchanged foreign-key patch together with an operator-class deletion patch and raised the unused, publicly declared defGetStringList function as another possible cleanup in #9.
- Tom confirmed both removals and explained his extra comment deletion while retaining the rtree fallback in #10 and #11; he favored keeping defGetStringList for possible future use in #12.
- Daniel acknowledged the missed comment in #13, leaving both submitted cleanup changes committed and the rtree fallback and defGetStringList retained.