Search Results
https://dev.mysql.com/doc/refman/8.4/en/innodb-autocommit-commit-rollback.html
If autocommit mode is enabled, each SQL statement forms a single transaction on its own. By default, MySQL starts the session for each new connection with autocommit enabled, so MySQL does a commit after each SQL statement if that statement did not ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-compression-tuning.html
Most often, the internal optimizations described in InnoDB Data Storage and Compression ensure that the system runs well with compressed data. However, because the efficiency of compression depends on the nature of your data, you can make decisions ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-data-encryption.html
InnoDB supports data-at-rest encryption for file-per-table tablespaces, general tablespaces, the mysql system tablespace, redo logs, and undo logs. You can set an encryption default for schemas and general tablespaces; this permits DBAs to control ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-file-per-table-tablespaces.html
A file-per-table tablespace contains data and indexes for a single InnoDB table, and is stored on the file system in a single data file. File-per-table tablespace characteristics are described under the following topics in this section: ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-information-schema-fulltext_index-tables.html
INNODB_FT_BEING_DELETED: Provides a snapshot of the INNODB_FT_DELETED table; it is used only during an OPTIMIZE TABLE maintenance operation. When OPTIMIZE TABLE is run, the INNODB_FT_BEING_DELETED table is emptied, and DOC_ID values are removed from ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-information-schema-metrics-table.html
The INNODB_METRICS table provides information about InnoDB performance and resource-related counters. SET GLOBAL innodb_monitor_disable = [counter-name|module_name|pattern|all]; innodb_monitor_reset: Resets counter values to zero. SET GLOBAL ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-locking-reads.html
If you query data and then insert or update related data within the same transaction, the regular SELECT statement does not give enough protection. Other transactions can update or delete the same rows you just queried. InnoDB supports two types of ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-locking.html
Shared and Exclusive Locks Intention Locks Record Locks Gap Locks Next-Key Locks Insert Intention Locks AUTO-INC Locks Predicate Locks for Spatial Indexes Shared and Exclusive Locks InnoDB implements standard row-level locking where there are two ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-locks-set.html
A locking read, an UPDATE, or a DELETE generally set record locks on every index record that is scanned in the processing of an SQL statement. It does not matter whether there are WHERE conditions in the statement that would exclude the row. InnoDB ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-tablespace-autoextend-size.html
By default, when a file-per-table or general tablespace requires additional space, the tablespace is extended incrementally according to the following rules: If the tablespace is less than an extent in size, it is extended one page at a time. If ...