PDF (US Ltr)
- 3.2Mb
PDF (A4)
- 3.2Mb
Search Results
https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-2.html
Low and high water marks are critical to detect workload spikes, overall workload stability, and possible memory leaks. (Bug #16759605) InnoDB: Valgrind testing returned memory leak errors which resulted from a regression introduced by the fix for ... Note This is a milestone release, for use at your own ...
https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-8.html
(Bug #21310520) InnoDB: A regression introduced in MySQL 5.7.2 caused an innochecksum-related memory leak. (Bug #20938115) InnoDB: A memory leak occurred when a foreign key constraint object was loaded with the parent table while the child table ...
https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-6.html
(Bug #74206, Bug #19729266) A new CMake option, WITH_MSCRT_DEBUG, is available to control Visual Studio CRT memory leak tracing. (Bug #20451454) On Linux, trying to install a .dll plugin (intended for Windows) resulted in a memory leak. (Bug ...
https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-9.html
Previously, it was necessary to call mysql_thread_end() for each mysql_thread_init() call to avoid a memory leak. mysql_thread_end() must be called for each mysql_thread_init() call to avoid a memory leak. If this occurred for a statement executed ... Audit Log Notes C API Notes Compilation Notes Deprecation and Removal Notes Performance Schema Notes Plugin Notes Security Notes Server Administration Spatial Data Support sys Schema Notes Functionality Added or Changed Bugs Fixed Audit Log Notes Some events cannot be ...
https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-4.html
(Making a backup before the upgrade is a prudent precaution in any case.) In Memoriam This release is dedicated to the memory of two young engineers of the MySQL Engineering family, Astha and Akhila, whom we lost while they were in their early ...
https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-3.html
(Bug #17848838, Bug #16511145) InnoDB: A regression introduced by the fix for Bug#17371537 resulted a memory leak for memcached insert operations. (Bug #17400687) In the Performance Schema memory instrumentation, statistics collected for memory-free ... Note This is a milestone release, for use at your own ...
https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-1.html
(Bug #16066637) Replication: Using the --replicate-* options (see Replica Server Options and Variables) could in some cases lead to a memory leak on the slave. (Bug #16043173) The query parser leaked memory for some syntax errors. Failure of CREATE ... Note This is a milestone release, for use at your own ...
https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-21.html
(Bug #25940184) Replication: In a multi-source replication topology, a memory leak could occur on the slave when binlog_rows_query_log_events was enabled on the master, and a statement already applied from another channel was skipped on the slave.
https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-10.html
(Bug #76795, Bug #68953, Bug #20938915, Bug #16666407) Microsoft Windows: Querying views on Windows could lead to memory leaks. ON DUPLICATE KEY UPDATE could result in a memory leak when executed as a prepared statement. (Bug #78593, Bug #21907297) ... Deprecation and Removal Notes Security Notes Functionality Added or Changed Bugs Fixed Deprecation and Removal Notes InnoDB: The innodb_support_xa system variable, which enables support for two-phase commit in XA transactions, is ...
https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-19.html
The leak happened when processing fake rotate events, or when using --raw and the destination log file could not be created. The leak only occurred when processing events from a remote server. (Bug #25451091) MySQL compilation in different ...