MySQL 5.7 Release Notes - Download - MySQL

More documents

Recommendations

Info

MySQL 5.7 Release Notes• Clients can request notification when there is a change to any of the session state-related valuesjust listed, in the form of a flag that is set in the OK packet received from the server after thechange occurs. To control notification, enable or disable the session_track_state_changesystem variable. This variable is disabled by default.• Clients can request notification of changed values for certain specific types of session stateinformation:• The default schema name. To control notification, enable or disable thesession_track_schema system variable. This variable is enabled by default.• The session values of system variables. Notification occurs for the system variables named bythe session_track_system_variables system variable. By default, notification is enabledfor time_zone, autocommit, character_set_client, character_set_results, andcharacter_set_connection. (The latter three variables are those affected by SET NAMES.)• To enable applications to extract the state-change information returned by the server, the MySQLC API includes a pair of functions:• mysql_session_track_get_first() fetches the first state-change information receivedfrom the server.• mysql_session_track_get_next() fetches any remaining statechangeinformation received from the server. Following a successful call tomysql_session_track_get_first(), call this function repeatedly as long as it returnssuccess.• Because there are new API functions, the client library ABI version is now 18.3. Shared librarynames now include 18.3 where appropriate.• The mysqltest program has enable_session_track_info anddisable_session_track_info commands to enable and disable tracking of session statechangeinformation.For more information, see Server System Variables and mysql_session_track_get_first().For information about the structure of the OK packet used to convey state-change information, seeOK_Packet.• mysqlbug, an obsolete program for generating bug reports, has been removed from the sourcecode.Bugs Fixed• Incompatible Change: Old clients (older than MySQL 5.5.7) failed to parse authenticationdata correctly if the server was started with the --default-authenticationplugin=sha256_passwordoption.(Bug #17495562)NoteAs a result of this bug fix, MySQL 5.6.16 clients cannot connect to a 5.6.17server using an account that authenticates with the sha256_passwordplugin. Similarly, MySQL 5.7.3 clients cannot connect to a 5.7.4 server usingan account that authenticates with the sha256_password plugin.• Important Change; InnoDB; Partitioning: The FLUSH TABLES statement's FOR EXPORT option isnow supported for partitioned InnoDB tables. (Bug #16943907)22
MySQL 5.7 Release Notes• InnoDB; Replication: Attempting to reset a replication slave while innodb_force_recoveryis greater than 0 would return a cryptic error message: ERROR(1030) HY000: Got error -1from storage engine. The error message has been changed to: ERROR HY000: Operationnot allowed when innodb_force_recovery > 0. Replication options such as --relaylog-info-repository=TABLEand --master-info-repository=TABLE store informationin tables in InnoDB. When innodb_force_recovery is greater than 0, replication tables cannotbe updated which may cause replication administration commands to fail. (Bug #17287443, Bug#69907)• InnoDB; Replication: An INSERT ...ON DUPLICATE KEY UPDATE statement run on a table withmultiple unique indexes would sometimes cause events to be incorrectly written to the binary log.(Bug #11758237, Bug #50413)• InnoDB; Replication: Using the InnoDB memcached plugin (see InnoDB Integration withmemcached) with innodb_api_enable_binlog set to 1 caused the server to leak memory. (Bug#70757, Bug #17675622)• InnoDB: trx_undo_truncate_start would write to the redo log for temporary undo logsegments, resulting in a purge thread assertion. (Bug #18252937)• InnoDB: A !sync_check_iterate(check) assertion occurred in fts_create_doc_id()during an INSERT operation. (Bug #18253210)• InnoDB: The GCC 4.4 Compiler would emit a bogus warnings about InnoDB parsing functions,indicating that output is uninitialized. (Bug #18192536)• InnoDB: log_mutex_exit should be called before log_buffer_extend when the log buffermutex is held. (Bug #18202904)• InnoDB: InnoDB would write to the redo log for some operations on temporary tablespaces. (Bug#18226934)• InnoDB: Doublewrite buffer error messages referenced page numbers in an inconsistent manner.(Bug #18242594)• InnoDB: The truncate_t::drop_indexes and truncate_t::create_indexes methodswould disable redo logging when modifying the system tablespace. (Bug #18236000)• InnoDB: Unused parameters and variables along with disabled functionality has been removed fromredo log code. This patch also includes redo log code improvements including test enablement,addition of Valgrind instrumentation, and minor code refactoring. (Bug #18251675)• InnoDB: An invalid memmove in fts_query_fetch_document would cause a serious error. (Bug#18229433)• InnoDB: For full-text queries, a failure to check that num_token is less thanmax_proximity_item could result in an assertion. (Bug #18233051)• InnoDB: InnoDB would perform unnecessary redo log writes and flushing for temporarytablespaces. (Bug #18236692)• InnoDB: The user defined type, xid_t, was defined multiple times. (Bug #18251254)• InnoDB: To simplify code and reduce memory usage, InnoDB redo log scan records for file-leveloperations, previously stored in a hash table, are now processed immediately. (Bug #18180875)• InnoDB: The loader in some Solaris versions would refuse to start a GCC-compiled binary (such asthe mysqld binary) that uses the PAUSE assembler instruction. (Bug #18122171)• InnoDB: Temporary tablespace file size did not match the file size specified by --innodb-tempdata-file-pathdue to an error in file size allocation logic. (Bug #18141070)23
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 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?