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-backup.html
The key to safe database management is making regular backups. Hot and cold backups are physical backups that copy actual data files, which can be used directly by the mysqld server for faster restore. Using MySQL Enterprise Backup is the ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-compression-internals.html
This section describes some internal implementation details about compression for InnoDB tables. The information presented here may be helpful in tuning for performance, but is not necessary to know for basic use of compression. Compression ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-configuring-io-capacity.html
The InnoDB master thread and other threads perform various tasks in the background, most of which are I/O related, such as flushing dirty pages from the buffer pool and writing changes from the change buffer to the appropriate secondary indexes.
https://dev.mysql.com/doc/refman/8.4/en/innodb-information-schema-examples-compression-sect.html
Example 17.1 Using the Compression Information Schema Tables The following is sample output from a database that contains compressed tables (see Section 17.9, “InnoDB Table and Page Compression”, INNODB_CMP, INNODB_CMP_PER_INDEX, and ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-information-schema-innodb_cmp.html
The INNODB_CMP and INNODB_CMP_RESET tables provide status information about operations related to compressed tables, which are described in Section 17.9, “InnoDB Table and Page Compression”. These two tables have identical contents, but reading ...
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-performance-midpoint_insertion.html
Rather than using a strict LRU algorithm, InnoDB uses a technique to minimize the amount of data that is brought into the buffer pool and never accessed again. The goal is to make sure that frequently accessed (“hot”) pages remain in the buffer ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-performance-multiple_io_threads.html
InnoDB uses background threads to service various types of I/O requests. You can configure the number of background threads that service read and write I/O on data pages using the innodb_read_io_threads and innodb_write_io_threads configuration ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-preload-buffer-pool.html
To reduce the warmup period after restarting the server, InnoDB saves a percentage of the most recently used pages for each buffer pool at server shutdown and restores these pages at server startup. The percentage of recently used pages that is ...