Search Results
https://dev.mysql.com/doc/refman/8.4/en/innodb-benefits.html
InnoDB tables have the following benefits: If the server unexpectedly exits because of a hardware or software issue, regardless of what was happening in the database at the time, you don't need to do anything special after restarting the database.
https://dev.mysql.com/doc/refman/8.4/en/innodb-compression-tuning.html
The adaptive LRU algorithm attempts to balance the use of memory between compressed and uncompressed pages to take into account whether the workload is running in an I/O-bound or CPU-bound manner. Most often, the internal optimizations described in ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-compression-usage.html
The actual compression algorithm is not affected by the KEY_BLOCK_SIZE value; the value determines how large each compressed chunk is, which in turn affects how many rows can be packed into each compressed page. Compressed tables can be created in ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-deadlocks-handling.html
Note that the InnoDB instant deadlock detection algorithm also works in this case, because the serializing lock is a row-level lock. This section builds on the conceptual information about deadlocks in Section 17.7.5.2, “Deadlock Detection”. It ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-file-defragmenting.html
If the insertions into an index are always ascending and records are deleted only from the end, the InnoDB filespace management algorithm guarantees that fragmentation in the index does not occur. Random insertions into or deletions from a ...
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-next-key-locking.html
To prevent phantoms, InnoDB uses an algorithm called next-key locking that combines index-row locking with gap locking. The so-called phantom problem occurs within a transaction when the same query produces different sets of rows at different times. For example, if a SELECT is executed twice, but returns a row the second time that was not returned the first time, the row is a “phantom” ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-online-ddl-single-multi.html
Operations for which you specify ALGORITHM=COPY or old_alter_table=1, to force the table-copying behavior if needed for precise backward-compatibility in specialized scenarios. Before the introduction of online DDL, it was common practice to ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-performance-compression-oltp.html
This option is enabled by default to prevent corruption that could occur if a different version of the zlib compression algorithm is used during recovery. Traditionally, the InnoDB compression feature was recommended primarily for read-only or ...
https://dev.mysql.com/doc/refman/8.4/en/keyring-key-types.html
MySQL Keyring supports keys of different types (encryption algorithms) and lengths: The available key types depend on which keyring plugin is installed. The permitted key lengths are subject to multiple factors: General keyring loadable-function ...