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-and-mysql-replication.html
This is true whether you are using statement-based or row-based replication. It is possible to use replication in a way where the storage engine on the replica is not the same as the storage engine on the source. For example, you can replicate ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-disk-io.html
On other platforms, InnoDB still uses I/O threads, but the threads may actually wait for I/O requests to complete; this technique is known as “simulated” asynchronous I/O. This feature is only supported on Fusion-io hardware and is only enabled ... InnoDB uses asynchronous disk I/O where possible, by creating a number of threads to handle I/O operations, while permitting other database operations to proceed while the I/O is still in ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-information-schema-internal-data.html
This is not like user tables, where the data changes only when application-initiated updates occur. This buffer is refreshed only if more than 0.1 seconds has elapsed since the last time the buffer was read. The data needed to fill the three tables ... The data exposed by the transaction and locking tables (INNODB_TRX, INNODB_LOCKS, and INNODB_LOCK_WAITS) represents a glimpse into fast-changing ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-multiple-buffer-pools.html
This feature is typically intended for systems with a buffer pool size in the multi-gigabyte range. This option takes effect only when you set innodb_buffer_pool_size to a size of 1GB or more. For systems with buffer pools in the multi-gigabyte ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-online-ddl-limitations.html
This scenario can result in deadlocks as other transactions wait for the online DDL operation to finish. This is similar to the idea of a foreign key constraint check in InnoDB in which constraints must hold during a transaction. The following ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-performance-midpoint_insertion.html
This arrangement divides the LRU list into two segments, where the pages downstream of the insertion point are considered “old” and are desirable victims for LRU eviction. Increasing this value makes more and more blocks likely to age out faster ... Rather than using a strict LRU algorithm, InnoDB uses a technique to minimize the amount of data that is brought into the buffer pool and never accessed ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-performance-spin_lock_polling.html
If the mutex or rw-lock becomes available during this period, the thread can continue immediately, in the same time slice. InnoDB minimizes this issue by forcing a random delay between polls to desychronize polling activity. In this way, the ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-undo-logs.html
This type of undo log benefits performance by avoiding redo logging I/O. This leaves 96 rollback segments that can be assigned to transactions that modify data in regular tables. This occurs when the rollback segment assigned to a transaction runs ... An undo log is a collection of undo log records associated with a single read-write ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-undo-tablespaces.html
This option can only be configured when initializing the MySQL instance. Configuring Undo Tablespaces This procedure describes how to configure undo tablespaces. Use this statement to check the value of innodb_undo_tablespaces: mysql> SELECT ...
https://dev.mysql.com/doc/refman/5.7/en/keyring-functions-plugin-specific.html
For each keyring plugin-specific function, this section describes its purpose, calling sequence, and return value. For information about general-purpose keyring functions, see Section 6.4.4.8, “General-Purpose Keyring Key-Management Functions”.