MySQL 5.7 Release Notes - Download - MySQL

More documents

Recommendations

Info

MySQL 5.7 Release Notes• InnoDB: innodb_ft_result_cache_limit now has a hardcoded maximum value of4294967295 bytes or (2**32 -1). The maximum value was previously defined as the maximum valueof ulong. (Bug #18180057, Bug #71554)• InnoDB: InnoDB would fail to restore a corrupt first page of a system tablespace data file from thedoublewrite buffer, resulting in a startup failure. (Bug #18144349, Bug #18058884)• InnoDB: An UPDATE resulted in a memory access error in lock_rec_other_trx_holds_expl.The transaction list (trx_sys->rw_trx_list) was traversed without acquiring the transactionsubsystem mutex (trx_sys->mutex). (Bug #18161853)• InnoDB: TRUNCATE TABLE on Windows would report multiple 'chsize' returned OS error71 errors. (Bug #18176071, Bug #71173)• InnoDB: A regression introduced by Bug #14329288 would result in a performance degradationwhen a compressed table does not fit into memory. (Bug #18124788, Bug #71436)• InnoDB: In the case of a corrupted clustered index on a temporary table, the server would crashon an INSERT instead of returning an error. In the case of a corrupted clustered index on a normaltable, an error was not returned and the INSERT would succeed. (Bug #18064548)• InnoDB: Specifying an alternate directory for InnoDB tables using datadir and then moving .ibdfiles to the default MySQL data directory would result in a serious error when attempting a DROPTABLE operation. (Bug #18063570)• InnoDB: The UNIV_LOG_DEBUG debug flag, which is no longer fully functional, has been removed.(Bug #18080537)• InnoDB: A compilation error (unable to find string literal operator) was returnedwhen building in c++11 mode. (Bug #18082139)• InnoDB: INFORMATION_SCHEMA.INNODB_TRX contained a bogus transaction ID that did notmatch transaction ID values printed elsewhere. The method used to retrieve transaction IDs wasinconsistent. (Bug #18111007)• InnoDB: The maximum value for innodb_thread_sleep_delay is now 1000000microseconds. The previous maximum value (4294967295 microseconds on 32-bit and18446744073709551615 microseconds on 64-bit) was unnecessarily large. Becausethe maximum value of innodb_thread_sleep_delay is limited by the value set forinnodb_adaptive_max_sleep_delay (when set to a non-zero value), the maximumvalue for innodb_thread_sleep_delay is now the same as the maximum value forinnodb_adaptive_max_sleep_delay. (Bug #18117322)• InnoDB: The fil_node_create function would perform an unnecessary hash table lookup. (Bug#18116588)• InnoDB: When starting the server, unnecessary “checking space” log messages would be printedwhen processing the doublewrite buffer. (Bug #18101380)• InnoDB: A full-text tokenizer thread would terminate with an incorrect error message. (Bug#18021306)• InnoDB: Attempting to uninstall the InnoDB memcached plugin while the InnoDB memcachedplugin is still initializing would kill the InnoDB memcached daemon thread. Uninstall should wait untilinitialization is complete. (Bug #18038948)• InnoDB: In debug builds, creating a unique index on a binary column, with input data containingduplicate keys, would cause an assertion. (Bug #18010711)• InnoDB: Logging functions were not used consistently. The bug fix replaces occurrences offprintf(stderr, message) and fputs() with ib_logf(). Also, because ib_logf()emits a timestamp with each message, the bug fix removes unnecessary occurrences ofut_print_timestamp(). (Bug #17935793, Bug #17534737)24
MySQL 5.7 Release Notes• InnoDB: A boolean mode full-text search query would result in a memory access violation duringparsing. (Bug #17978763)• InnoDB: The srv_monitor_thread would crash in the lock_print_info_summary() functiondue to a race condition between the srv_monitor_thread and purge coordinator thread. (Bug#17980590, Bug #70430)• InnoDB: On Windows, a regression introduced in 5.7.3 would allow log writes during syncoperations, which should not be allowed due to an issue in some Windows environments. (Bug#17824101)• InnoDB: Due to a parser error, full-text search queries that include a sub-expression could return thewrong result. (Bug #17840768)• InnoDB: The innochecksum tool did not use a Windows-specific API to retrieve file sizeinformation, which resulted in an incorrect error message (Error: ibdata1 cannot be found)when the MySQL 5.6 innochecksum 2GB file size limit was exceeded. innochecksum nowprovides support for files larger than 2GB in both MySQL 5.6 and MySQL 5.7. (Bug #17810862, Bug#70936)• InnoDB: Due to a regression introduced by the fix for Bug#17371537, memory was not allocated forthe default memcached engine when using the default memcached engine as the backstore for datainstead of InnoDB. (Bug #17800829)• InnoDB: If a crash occurred while temporary tables are active, InnoDB would report an invalid errormessage on restart indicating that a temporary table does not exist in the InnoDB internal datadictionary. (Bug #17779729)• InnoDB: A page allocation for an undo log due would fail with a “table is full” error message insteadof an “undo log is full” error message. (Bug #17779822)• InnoDB: ut_free could be called more than once in succession. (Bug #17763472)• InnoDB: An index tree modification could result in a deadlock. (Bug #17754767)• InnoDB: Manipulating a table after discarding its tablespace using ALTER TABLE ... DISCARDTABLESPACE could result in a serious error. (Bug #17700280)• InnoDB: A race condition in DebugPolicy::enter() would cause a segmentation fault insync_array_cell_print. (Bug #17713784)• InnoDB: Persistent optimizer statistics would cause stalls due to latch contention. (Bug #17699331,Bug #70768)• InnoDB: MATCH() ... AGAINST queries that use a long string as an argument for AGAINST()could result in an error when run on an InnoDB table with a full-text search index. (Bug #17640261)• InnoDB: An InnoDB full-text search failure would occur due to an “unended” token. The string andstring length should be passed for string comparison. (Bug #17659310)• InnoDB: Databases names beginning with a digit or special character would cause a full-text search(FTS) parser error. (Bug #17607687)References: See also Bug #17607956.• InnoDB: For debug builds, the table rebuilding variant of online ALTER TABLE, when run on tableswith BLOB columns, would cause an assertion in the row_log_table_apply_update function.For normal builds, a DB_PRODUCTION error would be returned. (Bug #17661919)• InnoDB: Under certain conditions, a regression introduced by the fix for Bug #11758237 wouldcause an assertion error when INSERT ... ON DUPLICATE KEY UPDATE or REPLACEstatements encounter a DB_DUPLICATE_KEY error. (Bug #17604730)25
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 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 74 and 75:
MySQL 5.7 Release Notes• InnoDB:
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?