MySQL 5.7 Release Notes - Download - MySQL

More documents

Recommendations

Info

MySQL 5.7 Release NotesAborted_connects, Connection_errors_accept, Connection_errors_internal,Connection_errors_max_connections, Connection_errors_peer_addr,Connection_errors_select, Connection_errors_tcpwrap.• Incompatible Change: Several statement instruments in the setup_instruments table are usedby the Performance Schema during the early stages of statement classification before the exactstatement type is known. These instruments were renamed to more clearly reflect their “abstract”nature:Old Instrument Namestatement/com/statement/com/Querystatement/rpl/relay_logNew Instrument Namestatement/abstract/new_packetstatement/abstract/Querystatement/abstract/relay_logIn addition, statistics for abstract instruments are no longer collected in the following tables, becauseno such instrument is ever used as the final classification for a statement:events_statements_summary_by_thread_by_event_nameevents_statements_summary_by_account_by_event_nameevents_statements_summary_by_user_by_event_nameevents_statements_summary_by_host_by_event_nameevents_statements_summary_global_by_event_nameApplications that refer to the old instrument names must be updated with the new names. For moreinformation about the use of abstract instruments in statement classification, see PerformanceSchema Statement Event Tables. (Bug #16750433, Bug #17271055)• Incompatible Change: The EXPLAIN statement has been changed so that the effects of theEXTENDED and PARTITIONS keywords are always enabled. EXTENDED and PARTITIONS are stillrecognized, but are superfluous and have been deprecated. They will be removed from EXPLAINsyntax in a future MySQL release.EXPLAIN output differs as follows as a result of this change:• The filtered and partitions columns appear in EXPLAIN output regardless of whether theEXTENDED and PARTITIONS keywords are specified. This is an incompatible change forapplications that expect to identify column information by position rather than by name, and suchapplications will need adjustment.• SHOW WARNINGS immediately following EXPLAIN shows additional execution plan informationregardless of whether the EXTENDED keyword is specified. (An additional deprecation warning isincluded if the statement includes the EXTENDED or PARTITIONS keyword.)• Important Change; InnoDB: InnoDB now supports external full-text parser plugins. In orderto support InnoDB full-text parser plugins that are called in boolean mode, a new “position”member has been added to the MYSQL_FTPARSER__BOOLEAN_INFO structure. If you plan to usean existing full-text parser plugin that is called in boolean mode with MySQL 5.7.3 or later, you mustadd support for the new “position” member, which is described in Writing Full-Text Parser Plugins.Altering a MyISAM table with a full-text parser plugin to use InnoDB is also supported. For additionalinformation about full-text parser plugins, see Full-Text Parser Plugins.• InnoDB: The InnoDB memcached plugin now supports inserts and reads on mapped InnoDB tablesthat have an INTEGER defined as the primary key. (Bug #17315083, Bug #17203937)• Replication: Replication filtering rules can now be set dynamically on the slave using the SQLstatement CHANGE REPLICATION FILTER introduced in this release. This statement has thesame effect as starting the slave mysqld with one or more of the options --replicate-dodb,--replicate-ignore-db, --replicate-do-table, --replicate-ignore-table,42
MySQL 5.7 Release Notes--replicate-wild-do-table, --replicate-wild-ignore-table, and --replicaterewrite-db.For example, issuing the statement CHANGE REPLICATION FILTER REPLICATE_DO_TABLE =(d1.t2) is equivalent to starting the slave mysqld with --replicate-do-table='d1.t2'.CHANGE REPLICATION FILTER differs from the server options in that, to take effect, the statementrequires only that the slave SQL thread be stopped beforehand and restarted afterwards, using STOPSLAVE SQL_THREAD and START SLAVE SQL_THREAD, respectively.This statement leaves any existing replication filtering rules unchanged; to unset all filters of a giventype, set the filter to an empty list, as shown in this example:CHANGE REPLICATION FILTER REPLICATE_DO_DB = ();You can list multiple replication filtering rules in the same statement, separated by commas. Whenmultiple instances of the same rule are found, only the last instance is used.For more information, see CHANGE REPLICATION FILTER Syntax; see also How Servers EvaluateReplication Filtering Rules. (Bug #15877941, Bug #11752237, Bug #67362, Bug #43366)• Replication: Previously, with semisynchronous replication enabled, the master waited fora single slave acknowledgment per transaction before proceeding. A new system variable,rpl_semi_sync_master_wait_for_slave_count, enables the number of slaveacknowledgments required per transaction to be configured. The minimum (and default) value is 1.The maximum is 65,536. Performance is best for small values of this variable.• Overhead for Performance Schema instrumentation associated with thread creation was reduced.(Bug #17539520)• The Performance Schema now instruments the read/write lock Delegate::lock, which is used forthe following classes:Trans_delegateBinlog_storage_delegateBinlog_transmit_delegateBinlog_relay_IO_delegateA different instrument name is used for each subclass, to have distinct statistics for distinct uses. Theinstruments are visible in the schema.setup_instruments table and have these names:wait/synch/rwlock/sql/Trans_delegate::lockwait/synch/rwlock/sql/Binlog_storage_delegate::lockwait/synch/rwlock/sql/Binlog_transmit_delegate::lockwait/synch/rwlock/sql/Binlog_relay_IO_delegate::lock(Bug #17590161, Bug #70577)• Some dependencies between client-side plugin header files were removed:• The MYSQL_PLUGIN_EXPORT macro required by plugin declarations is now declared directly inmysql/client_plugin.h instead of getting the definition from mysql/plugin.h. That macrowas the only thing required by client-side plugins and declared in server-side header mysql/plugin.h, so including mysql/client_plugin.h in an application no longer requires theapplication to also include mysql/plugin.h.• mysql/plugin_trace.h no longer uses C_MODE_START or C_MODE_END. Consequently,including mysql/plugin_trace.h in an application no longer requires the application to alsoinclude my_global.h.43
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 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 78 and 79: MySQL 5.7 Release Notesdirectory. T
Page 82 and 83: MySQL 5.7 Release NotesThis fix mov
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:
MySQL 5.7 Release Notes• InnoDB:
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?