model-writtenrun 5952 - may be wrong, links go to the source messages. Commit-by-commit LLM analysis is in the Commits dialog.
- Hans Buschmann proposed VS2022 support using the existing VS2019 implementation as a model, reported successful PostgreSQL 14 x64 compilation and installation, requested backpatching, and left 32-bit build failures for a separate discussion in #1.
- Andrew Dunstan and Michael Paquier favored waiting for the official VS2022 release in #3 and #4; after Hans requested inclusion just before PostgreSQL's November maintenance releases in #5, Tom Lane opposed that timing in #6, and Andrew emphasized backpatching for buildfarm coverage without rushing in #7.
- Hans refreshed the preview version string and reported another successful x64 build in #8; Daniel Gustafsson then identified incorrect patch path prefixes and requested a patch against development HEAD in #9.
- Hans submitted a development-source revision with the released VS2022 version string and reported successful builds on two installations in #10, although independent testing of the resulting binaries was still requested.
- Michael Paquier reviewed the final submission in #11, identified README spacing and an unrelated LZ4 documentation change, and confirmed that the reported compiler warnings were already known.
- Michael committed #10 with those light cleanups as b2265d305d and announced backpatching through PostgreSQL 10 in #12, noting that branches 10 and 11 required VC2012Project inheritance adjustments.
- With support landed, Hans asked about EDB adopting VS2022 for PostgreSQL 15 in #13; Dave Page explained that this was unlikely because all bundled dependencies needed a consistent toolchain in #14, and the thread ended with confirmation that EDB's PostgreSQL 14 builds already included LZ4 in #16.