PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 297.2Kb
Man Pages (Zip)
- 402.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/innodb-adaptive-hash.html
If there are numerous threads waiting on rw-latches created in btr0sea.c, consider increasing the number of adaptive hash index partitions or disabling the adaptive hash index. The adaptive hash index enables InnoDB to perform more like an ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-benefits.html
You can create and drop indexes and perform other DDL operations with much less impact on performance and availability. InnoDB tables have the following benefits: If the server unexpectedly exits because of a hardware or software issue, regardless ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-best-practices.html
Run the server with the --sql_mode=NO_ENGINE_SUBSTITUTION option to prevent tables from being created with storage engines that you do not want to use. Specify a primary key for every table using the most frequently queried column or columns, or an ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-compression.html
Using the compression features of InnoDB, you can create tables where the data is stored in compressed form. This section provides information about the InnoDB table compression and InnoDB page compression features. The page compression feature is ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-consistent-read.html
A consistent read means that InnoDB uses multi-versioning to present to a query a snapshot of the database at a point in time. The query sees the changes made by transactions that committed before that point in time, and no changes made by later or ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-deadlocks.html
FOR UPDATE) in each transaction; create indexes on the columns used in SELECT ... A deadlock is a situation in which multiple transactions are unable to proceed because each transaction holds a lock that is needed by another one. Because all ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-dedicated-server.html
As of MySQL 8.0.14, fsync() is called after creating a new file, after increasing file size, and after closing a file, to ensure that file system metadata changes are synchronized. When the server is started with --innodb-dedicated-server, InnoDB ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-disk-io.html
InnoDB uses asynchronous disk I/O where possible, by creating a number of threads to handle I/O operations, while permitting other database operations to proceed while the I/O is still in progress. On Linux and Windows platforms, InnoDB uses the ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-enabling-monitors.html
When this option is used, InnoDB creates a file named innodb_status.pid in the data directory and writes output to it every 15 seconds, approximately. When InnoDB monitors are enabled for periodic output, InnoDB writes the output to mysqld server ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-limits.html
If you reduce the InnoDB page size to 8KB or 4KB by specifying the innodb_page_size option when creating the MySQL instance, the maximum length of the index key is lowered proportionally, based on the limit of 3072 bytes for a 16KB page size. This ...