MySQL 5.7 Release Notes - Download - MySQL

More documents

Recommendations

Info

MySQL 5.7 Release Notes• InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables using online DDL(ALGORITHM=INPLACE) for the following operations:• OPTIMIZE TABLE• ALTER TABLE ... FORCE• ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table)Online DDL support reduces table rebuild time and permits concurrent DML, which helps reduceuser application downtime. For additional information, see Overview of Online DDL.(Bug #13975225)• InnoDB: New global configuration parameters, innodb_status_output andinnodb_status_output_locks, allow you to dynamically enable and disable the standardInnoDB Monitor and InnoDB Lock Monitor for periodic output. Previously, enabling and disablingthese monitors for periodic output required creating and dropping specially named tables(innodb_monitor and innodb_lock_monitor). For additional information, see InnoDBMonitors.• InnoDB: The InnoDB Tablespace Monitor and InnoDB Table Monitor are removed in MySQL5.7.4. For the Tablespace Monitor, equivalent functionality will be introduced before the GArelease of MySQL 5.7. For the Table Monitor, equivalent information can be obtained from InnoDBINFORMATION_SCHEMA tables.• InnoDB: MySQL now includes a gb18030 character set that supports the China National StandardGB18030 character set. For more information about MySQL character set support, see CharacterSet Support.• Replication: The binary log dump thread has been optimized by removing unnecessary reallocationof the send buffer. Previously, memory was allocated then freed for every event sent to the slave,even when this was not strictly necessary. Following this optimization, the MySQL Server can makebetter use of hardware resources by having the dump thread employ adaptative memory allocation,which can also result in less CPU usage. (Bug #11747349, Bug #31932, Bug #11752288, Bug#43426, Bug #13727951)• Replication: Implemented separate threads for sending and receiving semisynchronous replicationacknowledgement signals, so that event streams and ACK streams can be sent and receivedsimultaneously. This should reduce many common delays and thus improve performance withsemisynchronous replication in a number of settings.• Replication: It is now possible in many cases to execute CHANGE MASTER TO without first issuingSTOP SLAVE. This capability is added by implementing the following changes in the behavior of theCHANGE MASTER TO statement, which now depends only on whether the slave SQL thread or slaveI/O thread is stopped, as described here:• If the SQL thread is stopped, you can execute CHANGE MASTER TO using the RELAY_LOG_FILE,RELAY_LOG_POS, and MASTER_DELAY options, even if the slave I/O thread is running. No otheroptions may be used with this statement when the I/O thread is running.• If the I/O thread is stopped, you can execute CHANGE MASTER TO using any of the options for thisstatement except RELAY_LOG_FILE, RELAY_LOG_POS, or MASTER_DELAY, even when the SQLthread is running. These three options cannot be used when the I/O thread is running.• Both the SQL thread and the I/O thread must be stopped before issuing CHANGE MASTER TO withMASTER_AUTO_POSITION = 1.If you are using statement-based replication and temporary tables, it is possible for a CHANGEMASTER TO statement following a STOP SLAVE statement to leave behind temporary tables onthe slave. As part of this set of improvements, a warning is now issued whenever this occurs. You18
MySQL 5.7 Release Notescan avoid this in such cases by making sure that Slave_open_temp_tables is equal to 0 prior toexecuting these statements.For more information, see CHANGE MASTER TO Syntax, and Switching Masters During Failover.• Performance Schema performance was improved in the following ways:• When a thread connects, reset of all per-thread statistics is now delayed until a statistic is actuallycollected. This lazy initialization benefits workloads with very short-lived sessions, for whichinstrumentation is disabled.• When a thread disconnects, the per-thread statistics are aggregated to a parent only for statisticsthat actually collected data. This optimization benefits workloads with very short-lived sessions, forwhich instrumentation is disabled.• For statement instrumentation, reset of an individual EVENT_NAME statistic is also now delayeduntil a statistic is actually collected. This benefits all workloads that contain only a few types ofstatements (SELECT, INSERT, UPDATE, DELETE, and so forth) from the very large set statementssupported in MySQL. Only statements for event names actually executed are aggregated ondisconnect.• The memory footprint of internal memory buffers is reduced, by removing some attributesreserved for future use, that were in fact not used. In particular, statistics for mutexes, rwlocks andconditions now need less memory.(Bug #18324285)• On Windows, NOMINMAX is set using the ADD_DEFINITIONS() CMake macro rather than inconfig.h.cmake so that it is set even without including my_config.h. (Bug #18192896)• On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can befound at runtime. (Bug #18235669)• CMake support for compiling MySQL with gcc on Solaris was improved. Binary distributions forSolaris now are built using gcc rather than Sun Studio, to enable compilation of code not handledby Sun Studio. The client programs and the client libraries except the embedded library are still builtusing Sun Studio.A consequence of this change is that on Solaris, mysql_config no longer provides argumentsfor linking with the embedded library, since this is now built using gcc instead of Sun Studio. Toget linking arguments for the embedded library, use the alternative script mysql_server_configinstead. (Bug #18146422, Bug #17826757)• The CHECK_FUNCTION_REPLACEMENT() CMake macro was removed from Windows.cmake andreplacement functions are set explicitly instead since the result of the check was already hard codedin WindowsCache.cmake. (Bug #18116661)• MySQL now compiles using Clang 3.4. (Bug #18047020)• In MySQL 5.7.1, the MySQL test suite mysql-test-run.sh program was modified to start theserver with InnoDB rather than MyISAM as the default storage engine. All tests in the MySQLtest suite were modified to include a force_default_myisam.inc file. This had to be donebecause most legacy test results were recorded with the MyISAM engine and failed with aresult difference if run with InnoDB. A project is underway to migrate these tests and removeforce_default_myisam.inc for tests that do not need MyISAM. In 5.7.4, the rpl and binlogsuites and parts of the main suite were migrated. (Bug #17902011)• Performance Schema instrumentation was added to capture GTIDs for transaction events. (Bug#17799147)• Performance Schema overhead was reduced for the pfs_lock implementation and the uses ofatomic operations in general. (Bug #17766582)19
Page 1 and 2: MySQL 5.7 Release NotesAbstractThis
Page 3: MySQL 5.7 Release NotesFor addition
Page 6 and 7: MySQL 5.7 Release Notesthe value of
Page 8 and 9: MySQL 5.7 Release Notes• InnoDB:
Page 10 and 11: MySQL 5.7 Release Notes• If the s
Page 12 and 13: MySQL 5.7 Release Notes• The C cl
Page 14 and 15: MySQL 5.7 Release Notes• The Perf
Page 16 and 17: MySQL 5.7 Release Notes• Installa
Page 20 and 21: MySQL 5.7 Release Notes• CMake no
Page 22 and 23: MySQL 5.7 Release Notes• Clients
Page 30 and 31: MySQL 5.7 Release Notesthe specifie
Page 32 and 33: MySQL 5.7 Release Notes• A memory
Page 34 and 35: MySQL 5.7 Release Notes• A LIMIT
Page 36 and 37: MySQL 5.7 Release Notes• The make
Page 38 and 39: MySQL 5.7 Release Notes• For loga
Page 40 and 41: MySQL 5.7 Release NotesThis informa
Page 42 and 43: MySQL 5.7 Release NotesAborted_conn
Page 44 and 45: MySQL 5.7 Release NotesApplications
Page 50 and 51: MySQL 5.7 Release Notes• Replicat
Page 52 and 53: MySQL 5.7 Release Notes• Within a
Page 54 and 55: MySQL 5.7 Release Notes• Reads of
Page 56 and 57: MySQL 5.7 Release Notesthe deprecat
Page 58 and 59: MySQL 5.7 Release NotesHere, the SE
Page 60 and 61: MySQL 5.7 Release Notes• The setu
Page 62 and 63: MySQL 5.7 Release NotesFor upgrades
Page 64 and 65: MySQL 5.7 Release NotesTrigger db_n
Page 66 and 67: MySQL 5.7 Release Notesused and pri
Page 68 and 69:
MySQL 5.7 Release Notes• CMake no
Page 70 and 71:
MySQL 5.7 Release Notes• Performa
Page 72 and 73:
MySQL 5.7 Release Notes• InnoDB:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
MySQL 5.7 Release Notesdirectory. T
Page 80 and 81:
MySQL 5.7 Release Notes• Replicat
Page 82 and 83:
MySQL 5.7 Release NotesThis fix mov
Page 84 and 85:
MySQL 5.7 Release Notes• Replicat
Page 86 and 87:
MySQL 5.7 Release Notes• INSERT .
Page 88 and 89:
MySQL 5.7 Release Notes• In debug
Page 90 and 91:
MySQL 5.7 Release Notes• When a p
Page 92 and 93:
MySQL 5.7 Release Notes• If an ac
Page 94 and 95:
MySQL 5.7 Release Notes• Full-tex
Page 96 and 97:
MySQL 5.7 Release Notes• Some sub
Page 98 and 99:
Page 100 and 101:
MySQL 5.7 Release Notes• If a use
Page 102 and 103:
MySQL 5.7 Release Notes• FLUSH•
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
MySQL 5.7 Release Notesto stop with
Page 110 and 111:
MySQL 5.7 Release Notes• Windows
Page 112 and 113:
MySQL 5.7 Release Notes• A mysys
Page 114 and 115:
MySQL 5.7 Release Notes• The obso
Page 116 and 117:
MySQL 5.7 Release Notes• Adding a
Page 118 and 119:
MySQL 5.7 Release Notesand reads op
Page 120 and 121:
MySQL 5.7 Release Notes• Cluster
Page 122:
122
show all

MySQL 5.7 Release Notes - Download - MySQL

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?