PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 256.4Kb
Man Pages (Zip)
- 361.2Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
If a high innodb_force_recovery value is required to start InnoDB, there may be corrupted data structures that could cause complex queries (queries containing WHERE, ORDER BY, or other clauses) to fail. In this case, you may only be able to run ...
https://dev.mysql.com/doc/refman/5.7/en/foreign-key-optimization.html
Depending on how the data is distributed, the queries might perform less I/O and take up less cache memory because the relevant columns are packed together on disk. (To maximize performance, queries try to read as few data blocks as possible from ...
https://dev.mysql.com/doc/refman/5.7/en/index-btree-hash.html
Understanding the B-tree and hash data structures can help predict how different queries perform on different storage engines that use these data structures in their indexes, particularly for the MEMORY storage engine that lets you choose B-tree or ...B-Tree Index Characteristics Hash Index Characteristics B-Tree Index Characteristics A B-tree index can be used for column comparisons in expressions that use the =, >, >=, <, <=, or BETWEEN ...
https://dev.mysql.com/doc/refman/5.7/en/information-schema-innodb-buffer-page-table.html
The INNODB_BUFFER_PAGE table provides information about each page in the InnoDB buffer pool. For related usage information and examples, see Section 14.16.5, “InnoDB INFORMATION_SCHEMA Buffer Pool Tables”. Do not query this table on a ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-benefits.html
Performance benefits are not limited to large tables with long-running queries. 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 ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-deadlock-example.html
The following example illustrates how an error can occur when a lock request causes a deadlock. First, client A creates a table containing one row, and then begins a transaction. The lock cannot be granted because it is incompatible with the S lock ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-information-schema-temp-table-info.html
INNODB_TEMP_TABLE_INFO provides information about user-created InnoDB temporary tables that are active in the InnoDB instance. It does not provide information about internal InnoDB temporary tables used by the optimizer. mysql> SHOW TABLES FROM ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-setup.html
When a key is requested and the associated value is not already in the memory cache, the value is automatically queried from the MySQL test.demo_test table. daemon_memcached_w_batch_size is set to 1 by default so that no uncommitted data is lost in ... This section describes how to set up the daemon_memcached plugin on a MySQL ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-txn.html
A strict isolation level ensures that data you retrieve is not rolled back or changed suddenly causing subsequent queries to return different values. This option is less appropriate when accessing the same tables through both memcached and SQL, ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-performance-optimizer-statistics.html
This section describes how to configure persistent and non-persistent optimizer statistics for InnoDB tables. Persistent optimizer statistics are persisted across server restarts, allowing for greater plan stability and more consistent query ...