MySQL 5.7 Release Notes - Download - MySQL

More documents

Recommendations

Info

MySQL 5.7 Release Notes• CMake now aborts the configuration process on Windows if a Visual Studio version earlier than 2010is used. (Bug #17730320)• A new CMake option, WITH_MSAN, permits enabling MemorySanitizer for compilers that support it.(Bug #17632319)• Previously, ALTER TABLE in MySQL 5.6 could alter a table such that the result had temporalcolumns in both 5.5 and 5.6 format. Now ALTER TABLE upgrades old temporal columns to 5.6format for ADD COLUMN, CHANGE COLUMN, MODIFY COLUMN, ADD INDEX, and FORCE operations.This conversion cannot be done using the INPLACE algorithm because the table must be rebuilt, sospecifying ALGORITHM=INPLACE in these cases results in an error. Specify ALGORITHM=COPY ifnecessary.When ALTER TABLE does produce a temporal-format conversion, it generates a message that canbe displayed with SHOW WARNINGS: TIME/TIMESTAMP/DATETIME columns of old formathave been upgraded to the new format. (Bug #17246318)• The mysql_version.h file defines two new macros, LIBMYSQL_VERSION andLIBMYSQL_VERSION_ID, that indicate the string and numeric forms of the client library version.• In the client library included with MySQL Server distributions, these macros have the samevalues as MYSQL_SERVER_VERSION and MYSQL_VERSION_ID. For example, in MySQL5.7.4, MYSQL_SERVER_VERSION and LIBMYSQL_VERSION are "5.7.4-m14", andMYSQL_VERSION_ID and LIBMYSQL_VERSION_ID are 50704.• In the client library included with Connector/C distributions, MYSQL_SERVER_VERSION andMYSQL_VERSION_ID have the values of the MySQL version on which the Connector/Cdistribution is based, whereas LIBMYSQL_VERSION and LIBMYSQL_VERSION_ID indicatethe Connector/C version. For example, Connector/C 6.1.3 is based on MySQL 5.7.4, soMYSQL_SERVER_VERSION and MYSQL_VERSION_ID have values of "5.7.4-m14" and 50704,whereas LIBMYSQL_VERSION and LIBMYSQL_VERSION_ID have values of "6.1.3" and60103.In addition, the mysql_get_client_info() and mysql_get_client_version() C APIfunctions in the client library now return values that reflect the type of distribution that provides theclient library:• In MySQL distributions, mysql_get_client_info() returns MYSQL_SERVER_VERSION andmysql_get_client_version() returns MYSQL_VERSION_ID. This is the same as before.• In Connector/C distributions, mysql_get_client_info() returns LIBMYSQL_VERSION andmysql_get_client_version() returns LIBMYSQL_VERSION_ID. Previously, these functionsreturned the MySQL version, the same as in MySQL distributions.(Bug #17171724)• Overhead was reduced for filesort comparison operations. (Bug #14635144)• Overhead was reduced for metadata lock acquisition for DML statements. (Bug #58627, Bug#11765641)• CMake now supports a -DTMPDIR=dir_name option to specify the default tmpdir value. Ifunspecified, the value defaults to P_tmpdir in . Thanks to Honza Horak for the patch.(Bug #68338, Bug #16316074)• Based on community feedback, the default value of 10 for the eq_range_index_dive_limitsystem variable has proven to be too low. The default has been raised to 200. (Bug #70586, Bug#17587952)20
MySQL 5.7 Release Notes• Code instrumented with Valgrind did not preallocate memory in alloc_root(), to help findbugs. This behavior is now also enabled if ASAN (address sanitizer) is used. (Bug #44582, Bug#11753184)• mysql_install_db provides a more informative diagnostic message when required Perl modulesare missing. (Bug #69844, Bug #18187451)• MySQL now supports server-side timeouts for execution of SELECT statements:• SELECT supports a MAX_STATEMENT_TIME option to specify a timeout for individual queries. Forexample:SELECT MAX_STATEMENT_TIME = 5000 id, name FROM my_table WHERE ...• The max_statement_time system variable specifies the timeout value for SELECT statementsexecuted within the session that include no MAX_STATEMENT_TIME option. If the value is 0,timeouts are not enabled.• The Max_statement_time_exceeded, Max_statement_time_set, andMax_statement_time_set_failed status variables provide information about SELECTstatements affected by timeouts.Timeout values are in milliseconds.For more information, see SELECT Syntax, and Server System Variables.Thanks to Davi Arnaut for the patch on which this feature is based. (Bug #68252, Bug #16271666)• The metadata locking subsystem implementation now uses lock-free hashing rather than a hashprotected by a mutex. An implication of this change is that the metadata_locks_cache_sizeand metadata_locks_hash_instances system variables no longer have any effect, so they aredeprecated and will be removed in a future MySQL release.• The deprecated IGNORE clause for ALTER TABLE has been removed and its use produces an error.• The metadata locking subsystem now uses a lock-free algorithm for acquiring and releasing lockstypical for DML statements. This gives better performance/scalability on multi-core machines inworkloads involving lots of small read-only transactions.• The server can now report session-state changes to client programs. Reportable session stateconsists of these values:• The default schema (database)• Session-specific values for system variables• User-defined variables• Temporary tables• Prepared statementsThe MySQL client/server protocol now includes tracker information so that session state changescan be detected. One use for the tracker mechanism is that it provides a means for MySQLConnectors, Fabric, and client applications to determine whether any session context is available toensure session migration from one server to another. (To change connections in a load-balancedenvironment, it is necessary to detect whether there is session state to take into consideration whendeciding whether a switch can be made.)The user interface to control the tracker and retrieve state-change information from it has thefollowing components, which enable implementation of state-change tracking on the client side:21
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 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

Create successful ePaper yourself

Delete template?

Save as template?