MySQL 5.7 Release Notes - Download - MySQL

More documents

Recommendations

Info

MySQL 5.7 Release Notesthe value of rpl_semi_sync_slave_enabled, but did so for every operation performed onthis thread, which had significant negative impact on performance. Now this check is made onlyonce, when the dump thread is started, which should noticeably improve the performance ofsemisynchronous replication in most cases. (Bug #17932935)• InnoDB: A code comment for the os_event_is_set function in storage/innobase/os/os0event.cc was incorrect. (Bug #18940008, Bug #72919)• InnoDB: Added debug assertions to the adaptive hash index code to check that the tablespace ID inbuffer blocks match the index space. (Bug #18965518, Bug #72986)• InnoDB: trx_cleanup_at_db_startup failed to reset trx->rsegs->m-redo content in debugcode. (Bug #18795594)• InnoDB: Removed unused function definitions and declarations from the InnoDB memcached API.(Bug #18815992, Bug #72723)• InnoDB: The innodb_memcached_config.sql configuration script would fail after runningthe mysql_secure_installation script, which removes the MySQL test database. Theinnodb_memcached_config.sql script now creates the test database if it does not exist. (Bug#18816381, Bug #72678)• InnoDB: Opening an parent table that has thousands of child tables could result in a longsemaphore wait condition. (Bug #18806829)• InnoDB: A regression introduced by the fix for Bug #11758237 resulted in a cursor->index->name == TEMP_INDEX_PREFIX assertion. (Bug #18723872)• InnoDB: For single item full-text searches, deleted documents were included inverse documentfrequency (IDF) calculations. (Bug #18711306, Bug #72548)• InnoDB: A failed in-place ALTER TABLE operation would leave behind non-unique temporary filenames in the data dictionary preventing future ALTER TABLE operations on the same table dueto temporary file name conflicts. To avoid this problem, temporary file names are made unique byappending a static global number that is initialized to a random distributed 32-bit number usingut_time() and ut_crc32(). The number is then incremented atomically for each assignedtemporary file name. Previously, temporary files were named using the format #sql-ibtid, wheretid is the table ID. Temporary files are now named using the format #sql-ibtid-inc, where tidis the table ID and inc is the incremented number. (Bug #18734396, Bug #72594)• InnoDB: On mysqld start, specifying multiple data files using the innodb_data_file_pathoption would return a Space id in fsp header error after data is written to the second file. (Bug#18767811)• InnoDB: The page_create function has been optimized to use simpler functions to initialize pages.(Bug #18704384)• InnoDB: An INSERT operation on a table with BLOB columns raised an assertion. (Bug #18646430)References: This bug is a regression of Bug #16963396.• InnoDB: A DELETE operation on a table with full-text search indexes raised an assertion. (Bug#18683832)References: See also Bug #14639605.• InnoDB: When calling the memcached flush_all command, InnoDB attempts to initialize aconnection and a transaction. If the transaction is in TRX_STATE_NOT_STARTED state, InnoDBwould fail to set CONN_DATA->CRSR_TRX to NULL, resulting in a serious error. (Bug #18652854)• InnoDB: When InnoDB is built as a shared library, attempting to load the InnoDB full-textsearch (FTS) INFORMATION_SCHEMA plugin would fail with a Can't open shared library'ha_innodb.so' error. (Bug #18655281, Bug #70178)6
MySQL 5.7 Release Notes• InnoDB: On startup, with innodb_file_per_table=ON, the page cleaner thread would raise asrv_get_active_thread_type() == SRV_NONE debug assertion when encountering an activemaster thread. (Bug #18598813)• InnoDB: After upgrading from 5.6.10 to MySQL versions up to and including MySQL 5.6.18, InnoDBwould attempt to rename obsolete full-text search auxiliary tables on server startup, resulting in anassertion failure. (Bug #18634201, Bug #72079)• InnoDB: After running OPTIMIZE TABLE on an InnoDB table with a spatial index, running aSELECT statement that uses the spatial index could result in a crash. (Bug #18619945, Bug #72361)References: This bug is a regression of Bug #13975225.• InnoDB: An INSERT operation on a table with GEOMETRY columns raised an assertion inrtr_page_split_and_insert(). (Bug #18644435)• InnoDB: The temporary tablespace file (ibtmp1) was held open by the page_cleaner thread andcould not be removed on startup, resulting in a hang. (Bug #18642372)• InnoDB: InnoDB would try to merge a b-tree change buffer for a dedicated undo tablespace. (Bug#18593561)• InnoDB: When innodb_file_per_table is enabled, full-text search index tables would becreated in the system tablespace rather than in tablespace of the parent table. This patch also addsa space ID for full-text search index tables. (Bug #18635485)• InnoDB: A DB_LOCK_WAIT during a foreign key check caused redundant delete marking, resultingin a failing assertion. (Bug #18451287)• InnoDB: TRUNCATE TABLE would write page-level redo logs during the DROP TABLE step of aTRUNCATE TABLE operation. (Bug #18511398)• InnoDB: The os_event_wait_time_low function would sometimes returnOS_SYNC_TIME_EXCEEDED before the sync time has elapsed. (Bug #18386498)• InnoDB: Running a SELECT on a partitioned table caused a memory access violation in memcpy().(Bug #18383840)References: See also Bug #18167648.• InnoDB: With UNIV_SYNC_DEBUG enabled, a late call to sync_check_enable() would result inan m_enabled assertion failure. (Bug #18433658)• InnoDB: InnoDB would write to the redo log for an IMPORT TABLESPACE operation before thetablespace import was complete. (Bug #18424134)• InnoDB: The InnoDB memcached plugin would call plugin_del without acquiring thelock_plugin mutex. This bug fix also addresses a race condition in ib_cursor_delete_row.(Bug #18409840)• InnoDB: With persistent statistics enabled, SHOW TABLE STATUS output and the TABLE_ROWScolumn of INFORMATION_SCHEMA.TABLES could report an incorrect number of tables rows fortables with externally stored pages. (Bug #18384390)• InnoDB: Added the C++ ostream mechanism for error logging. (Bug #18320915)• InnoDB: Code quality improvements for the redo log subsystem. (Bug #18345004)• InnoDB: The fix for Bug#17699331 caused a high rate of read/write lock creation and destructionwhich resulted in a performance regression. (Bug #18345645, Bug #71708)• InnoDB: A regression introduced by the fix for Bug#18069105 could result in a table corruption andfailing assertions. (Bug #18368345)7
Page 1 and 2: MySQL 5.7 Release NotesAbstractThis
Page 3: MySQL 5.7 Release NotesFor addition
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 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?