PDF (US Ltr)
- 43.2Mb
PDF (A4)
- 43.3Mb
Man Pages (TGZ)
- 295.2Kb
Man Pages (Zip)
- 400.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/innodb-buffer-pool-optimization.html
InnoDB maintains a storage area called the buffer pool for caching data and indexes in memory. Knowing how the InnoDB buffer pool works, and taking advantage of it to keep frequently accessed data in memory, is an important aspect of MySQL tuning.
https://dev.mysql.com/doc/refman/8.0/en/innodb-information-schema.html
InnoDB INFORMATION_SCHEMA tables provide metadata, status information, and statistics about various aspects of the InnoDB storage engine. You can view a list of InnoDB INFORMATION_SCHEMA tables by issuing a SHOW TABLES statement on the ...For ...
https://dev.mysql.com/doc/refman/8.0/en/optimizing-innodb-queries.html
Follow these guidelines for InnoDB indexes: Because each InnoDB table has a primary key (whether you request one or not), specify a set of primary key columns for each table, columns that are used in the most important and time-critical queries. To ...Do not create a separate secondary index for each column, because each query can only make use of one ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-and-mysql-replication.html
For example, you can replicate modifications to an InnoDB table on the source to a MyISAM table on the replica. MySQL replication is based on the binary log where MySQL writes SQL statements that modify data. Cascading actions for InnoDB tables on ... It is possible to use replication in a way where the storage engine on the replica is not the same as the storage engine on the ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-memcached-porting-memcached.html
This is because InnoDB performs best for large-scale insertions if primary key values are added in sorted order (as they are with auto-increment values). If you store several different classes of information using memcached, consider setting up a ...
https://dev.mysql.com/doc/refman/8.0/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. When deadlock detection is enabled (the default) ... A deadlock is a situation in which multiple transactions are unable to proceed because each transaction holds a lock that is needed by another ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-best-practices.html
Enable the innodb_file_per_table variable or use general tablespaces to put the data and indexes for tables into separate files instead of the system tablespace. Evaluate whether your data and access patterns benefit from the InnoDB table or page ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-backup-recovery.html
This section covers topics related to InnoDB backup and recovery. For information about backup techniques applicable to InnoDB, see Section 17.18.1, “InnoDB Backup”. For information about point-in-time recovery, recovery from disk failure or ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-transaction-model.html
The InnoDB transaction model aims to combine the best properties of a multi-versioning database with traditional two-phase locking. InnoDB performs locking at the row level and runs queries as nonlocking consistent reads by default, in the style of ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-monitor-types.html
There are two types of InnoDB monitor: The standard InnoDB Monitor displays the following types of information: Work done by the main background thread Semaphore waits Data about the most recent foreign key and deadlock errors Lock waits for ...