PDF (US Ltr)
- 35.0Mb
PDF (A4)
- 35.1Mb
Man Pages (TGZ)
- 255.5Kb
Man Pages (Zip)
- 360.4Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/partitioning-pruning.html
The core concept behind partition pruning is relatively simple, and can be described as “Do not scan partitions where there can be no matching values”. By doing so, it is possible to expend much less time and effort in finding matching rows than ...
https://dev.mysql.com/doc/refman/5.7/en/slow-query-log.html
The slow query log consists of SQL statements that take more than long_query_time seconds to execute and require at least min_examined_row_limit rows to be examined. The slow query log can be used to find queries that take a long time to execute ...
https://dev.mysql.com/doc/refman/5.7/en/sys-processlist.html
The MySQL process list indicates the operations currently being performed by the set of threads executing within the server. They provide more complete information than the SHOW PROCESSLIST statement and the INFORMATION_SCHEMA PROCESSLIST table, ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-table-wait-summary-tables.html
The table_io_waits_summary_by_table table has these grouping columns to indicate how the table aggregates events: OBJECT_TYPE, OBJECT_SCHEMA, and OBJECT_NAME. The only difference is the additional group column, INDEX_NAME, which corresponds to the ... The following sections describe the table I/O and lock wait summary tables: table_io_waits_summary_by_index_usage: Table I/O waits per index table_io_waits_summary_by_table: Table I/O waits per table table_lock_waits_summary_by_table: Table lock waits per table 25.12.15.7.1 The table_io_waits_summary_by_table Table The table_io_waits_summary_by_table table aggregates all table I/O wait events, as generated by the wait/io/table/sql/handler ...
https://dev.mysql.com/doc/refman/5.7/en/memory-storage-engine.html
The MEMORY storage engine (formerly known as HEAP) creates special-purpose tables with contents that are stored in memory. Because the data is vulnerable to crashes, hardware issues, or power outages, only use these tables as temporary work areas ...
https://dev.mysql.com/doc/refman/5.7/en/nested-join-optimization.html
The following discussion refers to the join syntax described in Section 13.2.9.2, “JOIN Clause”. The syntax of table_factor is extended in comparison with the SQL Standard. The latter accepts only table_reference, not a list of them inside a ...
https://dev.mysql.com/doc/refman/5.7/en/security-against-attack.html
To start mysqld as a different Unix user, add a user option that specifies the user name in the [mysqld] group of the my.cnf option file where you specify server options. When you connect to a MySQL server, you should use a password. Password ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-buffer-pool-flushing.html
InnoDB performs certain tasks in the background, including flushing of dirty pages from the buffer pool. Dirty pages are those that have been modified but are not yet written to the data files on disk. In MySQL 5.7, buffer pool flushing is ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-locking.html
Shared and Exclusive Locks Intention Locks Record Locks Gap Locks Next-Key Locks Insert Intention Locks AUTO-INC Locks Predicate Locks for Spatial Indexes Shared and Exclusive Locks InnoDB implements standard row-level locking where there are two ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-locks-set.html
A locking read, an UPDATE, or a DELETE generally set record locks on every index record that is scanned in the processing of an SQL statement. It does not matter whether there are WHERE conditions in the statement that would exclude the row. InnoDB ...