MySQL 5.7 Release Notes - Download - MySQL

More documents

Recommendations

Info

MySQL 5.7 Release Notes• If the slave used a database filter (--replicate-do-db or --replicate-ignore-db option),no empty transaction was generated.(Bug #71376, Bug #18095502, Bug #18145032)• Enabling optimizer trace could cause a server exit for queries with a subquery in a HAVING clause.(Bug #18791851)• Spatial operations on InnoDB tables could fail attempting to access nonexistent index statistics.(Bug #18743725)• (Bug #18715670)• mysql_secure_installation ignored options defined after an unrecognized option. (Bug#18659533)• The code for processing the gb18030 character set had a too-strict assertion for single-characterinvalid characters. (Bug #18700668)• Compiler flags were not passed to DTrace, causing problems for 32-bit builds cross-compiled on 64-bit platforms. (Bug #18593044)• The server could fail to properly reprepare triggers that referred to another table after that table wastruncated. (Bug #18596756, Bug #72446, Bug #18665853)• For conditions on the form t.key NOT IN (c1, c2, ...), if one or more of the c1, c2 wasNULL, the optimizer generated incorrect range predicates, possibly yielding incorrect results.The range optimizer would build predicates for empty in-lists (because NULL values are removedfrom NOT IN (in-list)). (Bug #18556403, Bug #18715670)• mysql_session_track_get_first() and mysql_session_track_get_next() returnedinformation only when the type argument was SESSION_TRACK_SYSTEM_VARIABLES, andreturned information for all types, not just SESSION_TRACK_SYSTEM_VARIABLES. Now they returninformation of the type requested and only that type. (Bug #18463441)• In debug builds, a qsort operation on decimal values could raise an assertion. (Bug #18486249)• For debug builds, an assertion was raised for attempts using a cursor within a stored routine to fetcha large value (INT) which cannot fit into a variable (TINYINT). (Bug #18484649)• In debug builds, subquery optimization could be overly aggressive about raising an assertion. (Bug#18486607)• In debug builds, MAKE_SET() within a GROUP BY clause raised an assertion. (Bug #18487060)• Queries that use AES_ENCRYPT(), AES_DECRYPT(), or RANDOM_BYTES() cannot be cached butwere permitted to enter the query cache. (Bug #18383169)• mysql_install_db could hang while reading /dev/random to generate a random rootpassword. (Bug #18395378)• EXPLAIN FOR CONNECTION showed an incorrect filtering value for dynamic range queries. (Bug#18395059)• Assigning some values to the session_track_system_variables system variable could causea server exit. (Bug #18405677)• For mysql_upgrade, specifying the --defaults-extra-file with a nonexisting file caused asegmentation fault on some platforms. (Bug #18443096)• The HAVE_IB_LINUX_FUTEX CMake check failed due to a missing include file. (Bug #18353271)10
MySQL 5.7 Release Notes• After a code reorganization in MySQL 5.7.4, ORDER BY for multiple-table UPDATE statements wasignored. (Bug #18352634)• In debug builds, lack of proper object initialization of decimal objects caused an assertion to beraised. (Bug #18335446)• Certain INFORMATION_SCHEMA queries could cause a server exit. (Bug #18319790)• Plugin registration code in the embedded server (compiled without the Performance Schema) failedfor plugins compiled with the Performance Schema. (Bug #18363910)• Improper linking of join caches by the optimizer could lead to a server exit. (Bug #18335908)• The addition in MySQL 5.7.4 of session state information to the OK packet of the client/serverprotocol caused the mysql->info member to be missing a terminating null terminator. (Bug#18349102)• UNCOMPRESSED_LENGTH() could return NULL when it should not have. (Bug #18335269)• If MySQL was built with the -DINSTALL_LIBDIR=lib64 option, mysql_config did not workif the MySQL package was unpacked into a location with a different installation prefix. Also,mysql_config did not work for some RPM builds because it used an incorrect installation prefix.(Bug #18382225)• The COM_RESET_CONNECTION command did not reset some session system variables:rand_seed1, rand_seed2, timestamp. Also, it did not clear warnings, and, although it reset theprofiling variable, it did not reset profiling information. (Bug #18329348, Bug #18329560, Bug#18328396, Bug #18329452)• On Windows, some test cases ran too slowly due to mysqltest not testing properly for servertermination. (Bug #18330694)• For indexes on prefixes or character string columns, index corruption could occur for assignment ofbinary data to the column due to improper character counting. (Bug #18359924)• Solaris-specific scripts were included in and installed by non-Solaris packages. (Bug #18305641)• On Windows, use of the gb18030_unicode_520_ci caused a server exit. (Bug #18271429)• innobase_strnxfrm() wrote one byte too many. (Bug #18277082)• EXPLAIN for some full-text queries could raise an assertion. (Bug #18313651)• For queries involving an AND of two geometry ranges, the optimizer could decide no index wasusable but try to use it anyway, resulting in a server exit. (Bug #18220153)• EXPLAIN on a query with an EXISTS subquery containing a UNION could cause a server exit.Multiple executions of a prepared EXPLAIN on a UNION of subqueries could cause a server exit.(Bug #18167356)• Executing a correlated subquery on an ARCHIVE table which has an AUTO_INCREMENT columncaused the server to hang. (Bug #18065452)• The client library could cause clients to exit due to incorrectly mapping the client error number to thecorresponding message, if reallocation of packet buffer memory occurred. (Bug #18080920)• For XA transactions, -1 could be assigned as the format ID part of an XID value, resulting inmishandling (server hang or exit) of concurrent XA statements. (Bug #18107853)• Calling mysql_get_server_version() with an invalid connection handler argument caused theclient to exit. Now it returns 0 and reports a CR_COMMANDS_OUT_OF_SYNC error. (Bug #18053212)• If the optimizer chose to perform an index scan, in some cases it could choose a noncovering ratherthan a covering index. (Bug #18035906)11
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 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?