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/innodb-deadlocks-handling.html
This section builds on the conceptual information about deadlocks in Section 14.7.5.2, “Deadlock Detection”. It explains how to organize database operations to minimize deadlocks and the subsequent error handling required in applications.
https://dev.mysql.com/doc/refman/5.7/en/innodb-enabling-monitors.html
When InnoDB monitors are enabled for periodic output, InnoDB writes the output to mysqld server standard error output (stderr) every 15 seconds, approximately. InnoDB sends the monitor output to stderr rather than to stdout or fixed-size memory ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-index-types.html
Each InnoDB table has a special index called the clustered index that stores row data. To get the best performance from queries, inserts, and other database operations, it is important to understand how InnoDB uses the clustered index to optimize ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-information-schema-internal-data.html
The data exposed by the transaction and locking tables (INNODB_TRX, INNODB_LOCKS, and INNODB_LOCK_WAITS) represents a glimpse into fast-changing data. This is not like user tables, where the data changes only when application-initiated updates ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-developing.html
Typically, writing an application for the InnoDB memcached plugin involves some degree of rewriting or adapting existing code that uses MySQL or the memcached API. With the daemon_memcached plugin, instead of many traditional memcached servers ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-monitor-types.html
There are two types of InnoDB monitor: The standard InnoDB Monitor displays the following types of information: Work done by the main background thread Semaphore waits Data about the most recent foreign key and deadlock errors Lock waits for ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-next-key-locking.html
The so-called phantom problem occurs within a transaction when the same query produces different sets of rows at different times. For example, if a SELECT is executed twice, but returns a row the second time that was not returned the first time, ...
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 ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-performance-multiple_io_threads.html
InnoDB uses background threads to service various types of I/O requests. You can configure the number of background threads that service read and write I/O on data pages using the innodb_read_io_threads and innodb_write_io_threads configuration ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-performance-schema.html
This section provides a brief introduction to InnoDB integration with Performance Schema. For comprehensive Performance Schema documentation, see Chapter 25, MySQL Performance Schema. You can profile certain internal InnoDB operations using the ...