PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 297.2Kb
Man Pages (Zip)
- 402.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/information-schema-innodb-trx-table.html
TRX_SCHEDULE_WEIGHT The transaction schedule weight assigned by the Contention-Aware Transaction Scheduling (CATS) algorithm to transactions waiting for a lock. The TRX_SCHEDULE_WEIGHT value is different from the TRX_WEIGHT value, which is computed ... The INNODB_TRX table provides information about every transaction currently executing inside InnoDB, including whether the transaction is waiting for a lock, when the transaction started, and the SQL statement the transaction is executing, if ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-information-schema-system-tables.html
You can extract metadata about schema objects managed by InnoDB using InnoDB INFORMATION_SCHEMA tables. Traditionally, you would get this type of information using the techniques from Section 17.17, “InnoDB Monitors”, setting up InnoDB monitors ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-online-ddl-failure-conditions.html
The failure of an online DDL operation is typically due to one of the following conditions: An ALGORITHM clause specifies an algorithm that is not compatible with the particular type of DDL operation or storage engine. A LOCK clause specifies a low ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-performance-read_ahead.html
InnoDB uses two read-ahead algorithms to improve I/O performance: Linear read-ahead is a technique that predicts what pages might be needed soon based on pages in the buffer pool being accessed sequentially. The SHOW ENGINE INNODB STATUS command ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-row-format.html
Table-rebuilding operations include ALTER TABLE operations that use ALGORITHM=COPY or ALGORITHM=INPLACE where table rebuilding is required. The row format of a table determines how its rows are physically stored, which in turn can affect the ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndbd-definition.html
Currently, the only partitioning algorithm is hashing and ordered indexes are local to each node. The NDB recovery algorithm uses a “fuzzy” checkpoint of the data together with the UNDO log, and then applies the REDO log to play back all changes ... The [ndbd] and [ndbd default] sections are used to configure the behavior of the cluster's data ...
https://dev.mysql.com/doc/refman/8.0/en/partitioning-hash.html
See Section 26.2.4.1, “LINEAR HASH Partitioning”, for a description of this algorithm. Partitioning by HASH is used primarily to ensure an even distribution of data among a predetermined number of partitions. To partition a table using HASH ...
https://dev.mysql.com/doc/refman/8.0/en/partitioning-key.html
See Section 26.2.4.1, “LINEAR HASH Partitioning”, for a description of this algorithm and its implications. Partitioning by key is similar to partitioning by hash, except that where hash partitioning employs a user-defined expression, the ...
https://dev.mysql.com/doc/refman/8.0/en/partitioning-linear-hash.html
MySQL also supports linear hashing, which differs from regular hashing in that linear hashing utilizes a linear powers-of-two algorithm whereas regular hashing employs the modulus of the hashing function's value. We call this value V; it can be ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-replication-connection-configuration-table.html
(CHANGE REPLICATION SOURCE TO option: SOURCE_COMPRESSION_ALGORITHMS, CHANGE MASTER TO option: MASTER_COMPRESSION_ALGORITHMS) For more information, see Section 6.2.8, “Connection Compression Control”. ZSTD_COMPRESSION_LEVEL The compression level ... This table shows the configuration parameters used by the replica for connecting to the ...