model-writtenrun 654 - may be wrong, links go to the source messages. Commit-by-commit LLM analysis is in the Commits dialog.
- Nathan Bossart proposed dropping pre-v10 server support from psql, pg_dump, pg_dumpall, and pg_upgrade for PostgreSQL 20, citing the maintenance burden and a policy of supporting at least ten previous major releases #1.
- Tom Lane supported the goal but requested separate functional and pgindent patches to make review mechanical where possible, and raised whether ancient pg_restore archive support should also be retired #2.
- Andrew Dunstan supported roughly five-year intervals between such removals and noted that ancient servers could use intermediate upgrades; Corey Huinker proposed documenting supported upgrade paths and preserving a way to recover old archives #3 #4.
- Nathan considered a longer support window for archive files, while Tom emphasized that an archive might be the only surviving copy and that removing compatibility code would require careful investigation; no pg_restore removal or upgrade-path table entered this series #5 #6 #7.
- Nathan split the work into three application patches plus pgindent, checked the multixact rewrite changes, and then restored two accidentally removed v11 conditionals in psql #8 #9.
- Andrew coordinated buildfarm readiness, Tom confirmed the PostgreSQL 20 policy decision while explicitly withholding endorsement of the patch details, and Andrew deployed the buildfarm adjustment #10 #11 #12 #13.
- After June rebases, Fujii Masao found a missed dump connection-version check, an incorrectly encoded pg_upgrade cutoff, surviving legacy upgrade branches, obsolete test conditions, and stale psql completion assumptions #14 #15 #16.
- Nathan incorporated those corrections, removed obsolete test guards rather than adding protection against unsupported test setups, and simplified publication/subscription completion; he deferred adding pg_dumpall minimum-version documentation because it was a separate additive change needing wording discussion #17.
- Nathan committed the final dump, upgrade, and psql patches unchanged apart from rebase context, then applied the submitted formatting patch, announcing completion in #19: 3a0a30884f, 14d8418083, 831bec4592, and d69fdf79b8 all derive from #17.
- Nathan subsequently noticed that AdjustUpgrade.pm still handled unsupported versions and posted a separate cleanup removing those branches and an unused helper #20.
- The cleanup landed unchanged as a71825973a, and Nathan's final confirmation leaves all submitted patches committed, with the separately discussed documentation and archive-support ideas unimplemented in this thread #21.