MySQL 5.7 Release Notes - Download - MySQL

More documents

Recommendations

Info

MySQL 5.7 Release Notes• The C client library could leak memory when client plugins were used. (Bug #17933308)• The CMake -DWITHOUT_PARTITION_STORAGE_ENGINE=1 option did not work.As part of fixing this problem, a preferred syntax for disabling storage engines wasimplmented. The syntax -DWITH_engine_STORAGE_ENGINE=0 is now preferred to -DWITHOUT_engine_STORAGE_ENGINE=1. For example, use:-DWITH_EXAMPLE_STORAGE_ENGINE=0-DWITH_FEDERATED_STORAGE_ENGINE=0-DWITH_PARTITION_STORAGE_ENGINE=0Rather than:-DWITHOUT_EXAMPLE_STORAGE_ENGINE=1-DWITHOUT_FEDERATED_STORAGE_ENGINE=1-DWITHOUT_PARTITION_STORAGE_ENGINE=1(Bug #17947926)• A BEFORE UPDATE trigger could insert NULL into a NOT NULL column. (Bug #17864349)• For debug builds, DROP FUNCTION with a too-long function name raised an assertion. (Bug#17903490)• A (rare) deadlock could occur between LOCK_thd_data and the InnoDB trx_sys mutex. Onethread could read a query string while it was being removed by another thread. (Bug #17606098)• Deadlock could occur between LOCK_thd_data and the InnoDB trx_sys mutex. (Bug#17606098)• mysqldump could create table definitions in the dump file that resulted in Too many columnserrors when reloading the dump file. (Bug #17477959)• On Windows, calling mysql_thread_init() call without mysql_init() caused the client toexit. windows. Now it returns a nonzero result because it is an error to call mysql_thread_init()before the client library is initialized with mysql_library_init(). (Bug #17514920)• Using LOAD DATA INFILE to load fixed-length data into a view could cause a server exit. (Bug#17458965)• The optimizer trace could cause a server exit in cases where a subquery was transformed away.(Bug #17458054)• If a query had both MIN()/MAX() and aggregate_function(DISTINCT) (for example,SUM(DISTINCT)) and was executed using Loose Index Scan, the result values of MIN()/MAX()were set improperly. (Bug #17217128)• For UNION statements, the rows-examined value was calculated incorrectly. This was manifest astoo-large values for the ROWS_EXAMINED column of Performance Schema statement tables (such asevents_statements_current). (Bug #17059925)• Row constructor arguments to INTERVAL() could cause a server exit. (Bug #16439419)• The change made in MySQL 5.7.0 to display the XID value in hexadecimal for XA RECOVER if itcontained nonprintable characters was reverted because it caused problems for some clients. Nowthe statement takes an optional CONVERT XID keyword so that clients can request the XID value inhexadecimal on demand. (Bug #14670465)• Use of a nonmulti-byte algorithm for skipping leading spaces in multi-byte strings could cause aserver exit. (Bug #12368495, Bug #18315770)• With big_tables enabled, queries that used COUNT(DISTINCT) on a simple join with a constantequality condition on a non-duplicate key returned incorrect results. (Bug #52582, Bug #11760197)12
MySQL 5.7 Release Notes• When MySQL runs as service on Windows, NTService.Stop() initiates shutdown and exit eventsduring shutdown. After a code reorganization in MySQL 5.7.3, a call to clean_up() was missed,resulting in initiation of crash recovery. (Bug #71104, Bug #17980260)• Some statements could be written to the slow query log twice. (Bug #68626, Bug #16467055)• LOAD DATA LOCAL INFILE could use all CPU if import errors occurred when there were no linedelimiters. (Bug #51840, Bug #11759519)• Deadlock could occur if three threads simultaneously performed INSTALL PLUGIN, SHOWVARIABLES, and mysql_change_user(). (Bug #71236, Bug #18008907)• mysql_config_editor exited when given an empty argument to the --login-path option. (Bug#71837, Bug #18311024, Bug #18830493)• MySQL did not compile with Bison 3. A workaround is to downgrade to Bison 2. (Bug #71250, Bug#18017820)• ER_CANT_CREATE_GEOMETRY_OBJECT was treated as a fatal error, thus not catchable withcondition handlers. (Bug #72064, Bug #18413646)• For mysqldump, dump and restore operations failed for database names that contained backslash('\'). Thanks for Xiaobin Lin for the patch. (Bug #71437, Bug #18109728)• mysqlslap accepted an --iterations option value of 0, which resulted in a divide-by-zero error.The minimum option value now is 1. Thanks to Tsubasa Tanaka for the patch. (Bug #72082, Bug#18430704)• For IN() predicates with values different from the key data value, the optimizer sometimes used atable scan when it could do a range scan. (Bug #71962, Bug #18364815)• Some comparisons between BIGINT signed and unsigned values could yield incorrect results. (Bug#72046, Bug #18408499)• On Windows, REPAIR TABLE and OPTIMIZE TABLE failed for MyISAM tables with .MYD files largerthan 4GB. (Bug #69683, Bug #17235179)• Uninstalling and reinstalling semisynchronous replication plugins while semisynchronous replicationwas active caused replication failures. The plugins now check whether they can be uninstalledand produce an error if semisynchronous replication is active. To uninstall the master-side plugin,there must be no semisynchronous slaves. To uninstall the slave-side plugin, there must be nosemisynchronous I/O threads running. (Bug #70391, Bug #17638477)• A statement of the following form broke row-based replication because it created a table having afield of data type BIGINT with a display width of 3000, which is beyond the maximum acceptablevalue of 255:CREATE TABLE t1 AS SELECT REPEAT('A',1000) DIV 1 AS a;(Bug #71179, Bug #17994219)• For non-debug builds of several client programs, the --help message did not correctly indicate thatthe --debug, --debug-check, and --debug-info apply only for debug builds. (Bug #66854, Bug#16272328)• In the DIGEST_TEXT column of Performance Schema statement events tables, references to systemvariables of the form @@var_name were stored as @ @ var_name. (Bug #71634, Bug #18304086)• Updates could fail to update all applicable rows in cases where multiple key values were identicalexcept for trailing spaces. (Bug #69684, Bug #17156940)13
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 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

Create successful ePaper yourself

Delete template?

Save as template?