and .. .. This new capability is one several that provide DBAs more complete control over password management. https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-34.html 7/59
Production 5.1 (名前はない) Release Candidate General Availability 5.5~5.7 Development Milestone Release Candidate General Availability 8.0 Development Milestone Release Candidate, General Availability N/A 13/59
General Availability(~8.0.33) General Availability (8.0.34~) 8.1 N/A N/A Innovation Release is GA(No maintenance release after GA) 8.2(maybe) N/A N/A Innovation Release is GA(No maintenance release after GA) 8.4(maybe) N/A N/A General Availability(Long Term Support) 14/59
5.5~5.7 Development Milestone Release Candidate General Availability 8.0 Development Milestone Release Candidate, General Availability(~8.0.33) General Availability (8.0.34~) Next LTS(ex.8.4) Innovation Release(ex. 8.0, 8.1, 8.2) Innovation Release (ex. 8.3), Release Candidate? General Availability(Long Term Support) 15/59
which includes 5 years of premier and 3 years of e xtended support. Innovation releases will be supported until the next major & minor release. <snip> - About every 2 years a new Long Term Support version will be released (blue). An exception is the 8.x LTS rel ease which will happen well before EOL of 8.0 Introducing MySQL Innovation and Long-Term Support (LTS) versions 19/59
between General Availability (GA) releases only. For MySQ L 8.1, it is required that you upgrade from a MySQL 8.0 GA release (8.0.11 or higher). Upgrades from non-GA releases of MySQL 8.0 are not supported. - Upgrading to the latest release in the series is recommended before upgrading to the next release series. For ex ample, upgrade to the latest MySQL 8.0 release before upgrading to MySQL 8.1. https://dev.mysql.com/doc/refman/8.1/en/upgrade-paths.html 8.0は8.0.11とそれ以降って書いてあるけど、8.0.30へのアップグレードも結構クラッシュしたみた いだから避けて8.0最新から行った方が良いと思う 本当に8.0.34とそれ以降で変な変更を入れないなら、8.0.34まで行っておけばあとは8.0.40だろうが8.0.41 だろうが少ないインパクトで行けるはず ‐ 23/59
in MySQL 8.1の内容は8.1.0のリリースノートとほぼ同じ ‐ 今後乖離が広がっていった時にWhat Is Newはどこから比べてNewになるのか？？ MySQL Bugs: #112039: Request for What Is New in the next LTS release ‐ 日本MySQLユーザ会 とみたさん のMySQL Parametersは8.1.0対応済 https://mysql-params.tmtms.net/mysqld/ ‐ 25/59
system variable now permits the configuration and enforcement of a minimum number of characters that users must change when attempting to replace their own MySQL account passwords. ‐ 33/59
added to the libmysqlclient.so shared library that enable developers to access a MySQL server binary log: mysql_binlog_open(), mysql_binlog_fetch(), and mysql_binlog_close(). ‐ 34/59
Since MySQL provides other means of performing database dumps and backups with the same or additional functionality, including mysqldump and MySQL Shell Utilities, the mysqlpump client utility program has become redundant, and is now deprecated ‐ 35/59
sync_relay_log_info server system variable is deprecated in this release, and getting or setting this variable or its equivalent startup option –sync-relay- log-info now raises a warning. ‐ 36/59
binlog_format server system variable is now deprecated, and subject to removal in a future version of MySQL. The functionality associated with this variable, that of changing the binary logging format, is also deprecated. ‐ 37/59
The group_replication_recovery_complete_at server system variable is now deprecated, and setting it produces a warning. You should expect its removal in a future release of MySQL. (WL #15460) ‐ 38/59
client library currently supports performing an automatic reconnection to the server if it finds that the connection is down and an application attempts to send a statement to the server to be executed. Now, this feature is deprecated and subject to removal in a future release of MySQL. ‐ The related MYSQL_OPT_RECONNECT option is still available but it is also deprecated. C API functions mysql_get_option() and mysql_options() now write a deprecation warning to the standard error output when an application specifies MYSQL_OPT_RECONNECT. (WL #15766) ‐ As of MySQL 8.0.34 and 8.1.0 ‘s libmysqlclients deprecates `MYSQL_OPT_RECONNECT` · Issue #354 · perl5-dbi/DBD-mysql 40/59
new mysql_reset_connection_nonblocking() C API function. It is the counterpart of the mysql_reset_connection() synchronous function, for use by applications that require asynchronous communication with the server. Our thanks to Meta for the contribution. (Bug #32202058, WL #15633) ‐ The new mysql_get_connect_nonblocking_stage() C API function permits applications to monitor the progress of asynchronous connections for the purpose of taking appropriate actions based on the progress. Our thanks to Meta for the contribution. (Bug #32202053, WL #15651) ‐ 44/59
use of the dollar sign ($) as the initial character of an unquoted identifier was deprecated in MySQL 8.0.32. In this release, the use of an unquoted identifier starting with the dollar sign and containing one or more dollar signs in addition to the first one generates a syntax error. ‐ 45/59
troubleshooting in the event of an excessively long server shutdown, this release introduces a number of new messages that are written to the MySQL error log during shutdown ‐ 46/59
is now possible to capture EXPLAIN FORMAT=JSON output in a user variable using a syntax extension added in this release. EXPLAIN FORMAT=JSON INTO var_name stmt works with any explainable statement stmt to store the output in the user variable var_name ‐ 47/59
Change: MySQL version numbers used in versioned comments now support a major version consisting of one or two digits (previously, only a single digit was supported for this value). ‐ 49/59
Change: Dropped support for Enterprise Linux 6 (and associated glibc 2.12 generic), SUSE 12, Debian 10, MacOS 12, Ubuntu 18.04 and 20.04, Windows 10 and Server 2012R2; and 32-bit versions are no longer built. ‐ 50/59
Replication: Any statement that fetches values of system status variables fetches them all, and acquires a read lock on them all as well. This meant that a SHOW STATUS started after one of the operations just listed was required to wait until the operation was complete before returning. Now in such cases, the statement fetching status variables immediately returns their cached values instead of waiting. (Bug #35373030) ‐ 51/59
Replication: Before it elects a new primary, group_replication_set_as_primary() waits for all transactions to finish, including all DML operations that are currently being processed. ‐ 52/59
Replication: For better diagnosis and troubleshooting of network instabilities, MySQL Group replication adds a number of variables in this release providing network, control message, and data message statistics for each member of Group Replication. ‐ 53/59
a SHOW PARSE_TREE statement in debug builds to display the JSON- formatted parse tree for a SELECT statement. ‐ This statement is not supported in release builds, and is available only in debug builds, or by compiling the server using -DWITH_SHOW_PARSE_TREE. (WL #15426) ‐ 56/59
invalid SSL server and CA certificates were not identified as problematic until after the server started or after an invalid certificate was loaded at runtime. ‐ 57/59
yoku0825
mochizuki875
drumnistnakano
shin1x1
kutsushitaneko
bgpat
kniino
lycorptech_jp
yuj1osm
hirotomotaguchi
duelist2020jp
shimacos
chanyou0311
marcelosomers
tenderlove
zakiyama
jmmastey
mongodb
lara
bluesmoon
garrettdimon
cromwellryan
chriscoyier
lynnandtonic
moore
