model-writtenrun 3320 - may be wrong, links go to the source messages. Commit-by-commit LLM analysis is in the Commits dialog.
- Thomas Munro proposed requiring LLVM 14 for PostgreSQL 18 and removing pre-opaque-pointer compatibility code because the represented operating systems needing older LLVM releases would reach end of support before PostgreSQL 18 shipped #1.
- Thomas identified Debian Bullseye's LLVM 11 CI images as a prerequisite blocker and proposed moving CI to Bookworm #2; he also retained the old pass manager because LLVM versions before 16 could not preserve the existing inline threshold through the replacement API #3.
- Peter Eisentraut supported the LLVM cutoff but questioned maintaining versioned llvm-config and clang searches #4, prompting Thomas to add a separate probe-removal patch ahead of the LLVM cleanup #5.
- After Peter endorsed taking the probe removal into PostgreSQL 17 #6, Thomas committed that component unchanged as 4dd29b6833 and parked the remaining LLVM patches for PostgreSQL 18 with a temporary Bookworm CI workaround #7.
- Nazir Bilal Yavuz replaced the workaround with a Bookworm update that restored 32-bit testing by correcting the Perl executable version, reporting that all tests passed while retaining Thomas's LLVM patches unchanged #8; Thomas agreed to handle the CI fixes #9.
- Ole Peder Brandtzæg noticed that the probe-removal commit left configure documentation advertising obsolete versioned searches and supplied a correction that deliberately preserved the accurate Meson documentation #10.
- Thomas accepted the documentation correction but initially deferred action until the release thaw #11, while Tom Lane clarified that documentation-only fixes were allowed during the freeze #13.
- Peter committed Ole's documentation patch with only paragraph rewrapping as 4baff50132 and announced its completion #14.
- With CI images updated, Peter reported successful CI testing of the two remaining LLVM patches after minor rebasing #15, then announced both committed and planned to contact affected buildfarm owners about upgrades #16.
- The thread ended with the proposed work reported landed; Thomas identified an ARM crash fix and JITLink work involving LLVM 20 as subsequent maintenance tasks #17.