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/information-schema-innodb-locks-table.html
The INNODB_LOCKS table provides information about each lock that an InnoDB transaction has requested but not yet acquired, and each lock that a transaction holds that is blocking another transaction. Although LOCK_ID currently contains TRX_ID, the ...Note This table is deprecated as of MySQL 5.7.14 and is removed in MySQL ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-linux-native-aio.html
InnoDB uses the asynchronous I/O subsystem (native AIO) on Linux to perform read-ahead and write requests for data file pages. With synchronous I/O, query threads queue I/O requests, and InnoDB background threads retrieve the queued requests one at ...This behavior is controlled by the innodb_use_native_aio configuration option, which applies to Linux systems only and is enabled by ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-online-ddl.html
The online DDL feature provides support for in-place table alterations and concurrent DML. Benefits of this feature include: Improved responsiveness and availability in busy production environments, where making a table unavailable for minutes or ...Less disk space usage and I/O overhead than the table-copy ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-performance-compression-oltp.html
Traditionally, the InnoDB compression feature was recommended primarily for read-only or read-mostly workloads, such as in a data warehouse configuration. The rise of SSD storage devices, which are fast but relatively small and expensive, makes ...
https://dev.mysql.com/doc/refman/5.7/en/insert-optimization.html
Ideally, you make a single connection, send the data for many new rows at once, and delay all index updates and consistency checking until the very end. See Section 8.5.5, “Bulk Data Loading for InnoDB Tables” for tips specific to InnoDB tables.
https://dev.mysql.com/doc/refman/5.7/en/is-null-optimization.html
MySQL can perform the same optimization on col_name IS NULL that it can use for col_name = constant_value. For example, MySQL can use indexes and ranges to search for NULL with IS NULL. This optimization does not occur in cases when the column ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-temptables.html
The discussion in the following paragraphs does not apply when binlog_format=ROW because, in that case, temporary tables are not replicated; this means that there are never any temporary tables on the replica to be lost in the event of an unplanned ...If you stop the replica server, the temporary tables needed by those updates are no longer available when the replica is ...
https://dev.mysql.com/doc/refman/5.7/en/subquery-materialization.html
For subquery materialization to be used in MySQL, the optimizer_switch system variable materialization flag must be enabled. (oe_1, oe_2, ..., oe_N) [NOT] IN (SELECT ie_1, i_2, ..., ie_N ...) The predicate has this form, when there is a single outer ... The optimizer uses materialization to enable more efficient subquery ...
https://dev.mysql.com/doc/refman/5.7/en/sys-innodb-buffer-stats-by-schema.html
These views summarize the information in the INFORMATION_SCHEMA INNODB_BUFFER_PAGE table, grouped by schema. Warning Querying views that access the INNODB_BUFFER_PAGE table can affect performance. Do not query these views on a production system ...
https://dev.mysql.com/doc/refman/5.7/en/sys-innodb-buffer-stats-by-table.html
These views summarize the information in the INFORMATION_SCHEMA INNODB_BUFFER_PAGE table, grouped by schema and table. Warning Querying views that access the INNODB_BUFFER_PAGE table can affect performance. Do not query these views on a production ...