-
Marko Mäkelä authored
InnoDB has a few hardcoded special table names: CREATE TABLE on one of these names will set flags inside InnoDB to enable additional debug output to the error log. DROP TABLE will clear the flags and stop the output. We are deprecating this awkward mechanism. Replacements are available as follows: innodb_monitor: Replace with SET GLOBAL innodb_status_output=ON|OFF; innodb_lock_monitor: Replace with SET GLOBAL innodb_status_output=ON|OFF; SET GLOBAL innodb_status_output_locks=ON|OFF; (CREATE/DROP TABLE innodb_lock_monitor is affecting both flags.) innodb_tablespace_monitor: innodb_table_monitor: There is no direct replacement for these. Use INFORMATION_SCHEMA.INNODB_SYS_* tables. innodb_mem_validate: Remove. This depends on UNIV_MEM_DEBUG, which is not normally enabled even in debug builds.
Marko Mäkelä authoredInnoDB has a few hardcoded special table names: CREATE TABLE on one of these names will set flags inside InnoDB to enable additional debug output to the error log. DROP TABLE will clear the flags and stop the output. We are deprecating this awkward mechanism. Replacements are available as follows: innodb_monitor: Replace with SET GLOBAL innodb_status_output=ON|OFF; innodb_lock_monitor: Replace with SET GLOBAL innodb_status_output=ON|OFF; SET GLOBAL innodb_status_output_locks=ON|OFF; (CREATE/DROP TABLE innodb_lock_monitor is affecting both flags.) innodb_tablespace_monitor: innodb_table_monitor: There is no direct replacement for these. Use INFORMATION_SCHEMA.INNODB_SYS_* tables. innodb_mem_validate: Remove. This depends on UNIV_MEM_DEBUG, which is not normally enabled even in debug builds.
Loading