Search Results
https://dev.mysql.com/doc/refman/8.4/en/information-schema-engines-table.html
In the latter case, the error log should contain a reason indicating why the option is disabled. This is particularly useful for checking whether a storage engine is supported, or to see what the default engine is. The ENGINES table has these ...
https://dev.mysql.com/doc/refman/8.4/en/information-schema-innodb-trx-table.html
TRX_LAST_FOREIGN_KEY_ERROR The detailed error message for the last foreign key error, if any; otherwise NULL. The INNODB_TRX table provides information about every transaction currently executing inside InnoDB, including whether the transaction is ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-auto-increment-handling.html
Notes When an AUTO_INCREMENT integer column runs out of values, a subsequent INSERT operation returns a duplicate-key error. InnoDB provides a configurable locking mechanism that can significantly improve scalability and performance of SQL ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-benchmarking.html
If a table relies on a feature that is specific to another storage engine, you receive an error. In this case, add the ENGINE=other_engine_name clause to the CREATE TABLE statement to avoid the error. If InnoDB is not the default storage engine, ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-buffer-pool-in-core-file.html
mysql> SET GLOBAL innodb_buffer_pool_in_core_file=OFF; If the innodb_buffer_pool_in_core_file variable is disabled but MADV_DONTDUMP is not supported by the operating system, or an madvise() failure occurs, a warning is written to the MySQL server ... A core file records the status and memory image of a running ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-compression-usage.html
When innodb_strict_mode is enabled (the default), CREATE TEMPORARY TABLE returns errors if ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE is specified. Compressed tables can be created in file-per-table tablespaces or in general tablespaces. The system ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-deadlocks-handling.html
It explains how to organize database operations to minimize deadlocks and the subsequent error handling required in applications. Information about each deadlock, not just the latest one, is recorded in the MySQL error log. This section builds on ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-deadlocks.html
If frequent deadlocks highlight a problem with transaction structure or application error handling, enable innodb_print_all_deadlocks to print information about all deadlocks to the mysqld error log. A deadlock is a situation in which multiple ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-init-startup-configuration.html
If a tablespace file is not found, InnoDB logs an error and continues the startup sequence. The first decisions to make about InnoDB configuration involve the configuration of data files, log files, page size, and memory buffers, which should be ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-online-ddl-space-requirements.html
If the operation takes a long time and concurrent DML modifies the table so much that the size of the temporary log file exceeds the value of innodb_online_alter_log_max_size, the online DDL operation fails with a DB_ONLINE_LOG_TOO_BIG error, and ...