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-sys-columns-table.html
For character columns in multibyte character sets, this length value is the maximum length in bytes needed to represent a definition such as VARCHAR(N); that is, it might be 2*N, 3*N, and so on depending on the character encoding. row ... The ...
https://dev.mysql.com/doc/refman/5.7/en/information-schema-innodb-sys-fields-table.html
The INNODB_SYS_FIELDS table has these columns: INDEX_ID An identifier for the index associated with this key field; the same value as INNODB_SYS_INDEXES.INDEX_ID. row *************************** INDEX_ID: 117 NAME: col1 POS: 0 Notes You must have ...
https://dev.mysql.com/doc/refman/5.7/en/information-schema-innodb-temp-table-info-table.html
row *************************** TABLE_ID: 38 NAME: #sql26cf_6_0 N_COLS: 4 SPACE: 52 PER_TABLE_TABLESPACE: FALSE IS_COMPRESSED: FALSE Notes This table is useful primarily for expert-level monitoring. Use the INFORMATION_SCHEMA COLUMNS table or the ...
https://dev.mysql.com/doc/refman/5.7/en/information-schema-processlist-table.html
For a comparison of this table with other sources, see Sources of Process Information. This is the same value displayed in the Id column of the SHOW PROCESSLIST statement, displayed in the PROCESSLIST_ID column of the Performance Schema threads ...
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 ...