PDF (US Ltr)
- 35.0Mb
PDF (A4)
- 35.1Mb
Man Pages (TGZ)
- 254.9Kb
Man Pages (Zip)
- 359.9Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/explain-extended.html
For SELECT statements, the EXPLAIN statement produces extra (“extended”) information that is not part of EXPLAIN output but can be viewed by issuing a SHOW WARNINGS statement following EXPLAIN. The Message value in SHOW WARNINGS output displays ...
https://dev.mysql.com/doc/refman/5.7/en/external-locking.html
External locking is the use of file system locking to manage contention for MyISAM database tables by multiple processes. External locking is used in situations where a single process such as the MySQL server cannot be assumed to be the only ...
https://dev.mysql.com/doc/refman/5.7/en/index-condition-pushdown-optimization.html
Index Condition Pushdown (ICP) is an optimization for the case where MySQL retrieves rows from a table using an index. Without ICP, the storage engine traverses the index to locate rows in the base table and returns them to the MySQL server which ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-buffer-pool-resize.html
You can configure InnoDB buffer pool size offline or while the server is running. For additional information about configuring buffer pool size online, see Configuring InnoDB Buffer Pool Size Online. When increasing or decreasing ...
https://dev.mysql.com/doc/refman/5.7/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/5.7/en/innodb-information-schema-understanding-innodb-locking.html
When a transaction updates a row in a table, or locks it with SELECT FOR UPDATE, InnoDB establishes a list or queue of locks on that row. Similarly, InnoDB maintains a list of locks on a table for table-level locks. If a second transaction wants to ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-benefits.html
The combination of InnoDB tables and memcached offers advantages over using either by themselves. Direct access to the InnoDB storage engine avoids the parsing and planning overhead of SQL. Running memcached in the same process space as the MySQL ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-txn.html
Unlike traditional memcached, the daemon_memcached plugin allows you to control durability of data values produced through calls to add, set, incr, and so on. By default, data written through the memcached interface is stored to disk, and calls to ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-online-ddl-performance.html
Online DDL improves several aspects of MySQL operation: Applications that access the table are more responsive because queries and DML operations on the table can proceed while the DDL operation is in progress. Reduced locking and waiting for MySQL ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-undo-logs.html
An undo log is a collection of undo log records associated with a single read-write transaction. An undo log record contains information about how to undo the latest change by a transaction to a clustered index record. If another transaction needs ...