model-writtenrun 8330 - may be wrong, links go to the source messages. Commit-by-commit LLM analysis is in the Commits dialog.
- Peter Eisentraut opened the discussion by asking whether libpq should adopt the server's new TLSv1.2 minimum for PostgreSQL 13, rather than accepting older protocols by default #1.
- Daniel Gustafsson initially defended compatibility with old servers and supplied a comment documenting that rationale #2; Magnus Hagander then pointed out that Debian's OpenSSL configuration already imposed TLSv1.2, making the effective default dependent on the platform #3.
- Peter argued that client and server defaults needed a consistent rationale and noted that TLSv1.2 support dated to 2012 #5, while Daniel and Michael Paquier remained concerned about breaking existing pg_dump connections to old servers #7 #8.
- Bruce Momjian suggested clearer errors for incompatible protocol requirements #6; Tom Lane proposed explanatory hints #9, and Michael identified OpenSSL error codes that could trigger them #10.
- Robert Haas argued that secure defaults would benefit more users than preserving implicit compatibility with very old SSL installations #11, persuading Tom to support the change if failures could be explained clearly #12.
- Tom's experiments confirmed that RHEL8 already required TLSv1.2 through openssl.cnf, strengthening the case for an explicit, platform-independent libpq default #13; Daniel consequently supported raising the default and improving server-side diagnostics too #15.
- Tom posted client and server protocol-version hints with hard-coded fallback bounds #17, then revised them to infer supported bounds through macros in common/openssl.h and included a separate TLSv1.2 default patch after finding OpenSSL's getter APIs unsuitable #18.
- Daniel reviewed both patches, requested SSL_R_UNKNOWN_PROTOCOL handling and a comment explaining that SSLv2 and SSLv3 were already disabled, and raised the need for accurate PostgreSQL 13 release notes #19; Tom accepted the corrections and said release-note updates would normally follow later in beta #20.
- Tom committed the unchanged default-change component of #18 as 6e682f61a5, then committed its hints component with Daniel's corrections and revised error-code explanations as b63dd3d88f; both changes were backpatched to PostgreSQL 13.
- The thread ended with Tom confirming that both patches had been pushed and explaining that an openssl.cnf restriction had initially confused his interpretation of one error code #21; the original comment preserving an unset client default #2 was superseded by the decision to require TLSv1.2.