model-writtenrun 9117 - may be wrong, links go to the source messages. Commit-by-commit LLM analysis is in the Commits dialog.
- Victor Wagner reported that PostgreSQL 12 failed to compile with SUSE's OpenSSL 0.9.8j because TLS version constants existed without corresponding SSL_OP_NO_* flags #1; Michael Paquier reproduced the failure with upstream OpenSSL's 0.9.8 branch #2, and Victor submitted guards based on TLS_MAX_VERSION #3.
- Alvaro Herrera proposed dropping obsolete OpenSSL support #4, but Tom Lane argued that PostgreSQL 12 was too close to release to change its requirements #5, and Michael supported fixing compatibility while leaving a future support-policy change open #8.
- Tom questioned whether TLS_MAX_VERSION was consistently available #6, while Peter Eisentraut initially suspected vendor modifications #7; Michael traced the constants to later upstream 0.9.8 releases #9 and found an incorrect TLS 1.2 comparison in Victor's TLS 1.3 guard #10.
- Tom rejected using nominal OpenSSL version numbers because vendor patches make them unreliable #11, and Peter showed that upstream had deprecated TLS_MAX_VERSION #13, then supplied a replacement using direct SSL_OP_NO_* checks and propagated failure returns #14.
- Michael reported successful compilation and SSL tests across OpenSSL 0.9.8 through 1.1.1, requested explicit error reporting and a matching explanatory comment, and identified a separate channel-binding test failure to address outside this patch #16.
- Peter wanted the compatibility wrappers to preserve OpenSSL's error behavior #17, and Michael clarified that the requested FATAL/LOG reporting belonged in be_tls_init() after the wrapper calls #18.
- Peter committed 4e6f101e92 from #14 with the requested diagnostics and comment, confirming completion in #19; Michael acknowledged the result in #20, closing the compatibility fix while the separate channel-binding issue remained outside this thread.