![]() InnoDB support for two-phase commit in XA transactions is always enabled as of MySQL 5.7.10. ![]() InnoDB: The innodb_support_xa system variable, which enables support for two-phase commit in XA transactions, is deprecated. InnoDB: Enabling the new innodb_background_drop_list_empty debug configuration option helps avoid test case failures by delaying table creation until the background drop list is empty. For more information, see Secure Connection Protocols and Ciphers. By default, MySQL attempts to use the highest TLS protocol version available, depending on which SSL library was used to compile the server and client, which key size is used, and whether the server or client are restricted from using some protocols by means of tls_version/-tls-version. The mysql_options() C API function has a new MYSQL_OPT_TLS_VERSION option that enables specifying from within the client library the TLS protocols permitted by a client program. On the client side, the -tls-version option enables specifying the TLS protocols permitted per client invocation. The tls_version system variable enables specifying at startup the TLS protocols permitted by the server. To enable TLSv1.2 support if you build from source, you must set the WITH_SSL CMake option to use OpenSSL. ![]() Because TLSv1.2 requires OpenSSL, support for this protocol is available in binary distributions only for MySQL Commercial Server, and not for MySQL Community Server (which is compiled using yaSSL). TLS support is now extended to enable a higher level of encrypted connection security: when compiled using OpenSSL 1.0.1 or higher, MySQL supports the TLSv1, TLSv1.1, and TLSv1.2 protocols when compiled using the bundled version of yaSSL, MySQL supports the TLSv1 and TLSv1.1 protocols. Previously, MySQL supported only the TLSv1 protocol for encrypting secure connections. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |