PDF (US Ltr)
- 41.9Mb
PDF (A4)
- 42.0Mb
Man Pages (TGZ)
- 272.3Kb
Man Pages (Zip)
- 378.3Kb
Info (Gzip)
- 4.2Mb
Info (Zip)
- 4.2Mb
Search Results
https://dev.mysql.com/doc/refman/9.7/en/innodb-file-per-table-tablespaces.html
A file-per-table tablespace contains data and indexes for a single InnoDB table, and is stored on the file system in a single data file. File-per-table tablespace characteristics are described under the following topics in this section: ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-information-schema-compression-tables.html
There are two pairs of InnoDB INFORMATION_SCHEMA tables about compression that can provide insight into how well compression is working overall: INNODB_CMP and INNODB_CMP_RESET provide information about the number of compression operations and the ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-information-schema-examples.html
This section describes the use of locking information as exposed by the Performance Schema data_locks and data_lock_waits tables. Identifying Blocking Transactions It is sometimes helpful to identify which transaction blocks another. The tables ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-information-schema-internal-data.html
The data exposed by the transaction and locking tables (INFORMATION_SCHEMA INNODB_TRX table, Performance Schema data_locks and data_lock_waits tables) represents a glimpse into fast-changing data. This is not like user tables, where the data ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-information-schema-understanding-innodb-locking.html
When a transaction updates a row in a table, or locks it with SELECT FOR UPDATE, InnoDB establishes a list or queue of locks on that row. Similarly, InnoDB maintains a list of locks on a table for table-level locks. If a second transaction wants to ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-init-startup-configuration.html
The first decisions to make about InnoDB configuration involve the configuration of data files, log files, page size, and memory buffers, which should be configured before initializing InnoDB. Modifying the configuration after InnoDB is initialized ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-introduction.html
InnoDB is a general-purpose storage engine that balances high reliability and high performance. Unless you have configured a different default storage engine, issuing a CREATE TABLE statement without an ENGINE clause creates an InnoDB table. Key ...
https://dev.mysql.com/doc/refman/9.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. This behavior is controlled by the innodb_use_native_aio configuration option, which applies to Linux systems only and is ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-locking-reads.html
If you query data and then insert or update related data within the same transaction, the regular SELECT statement does not give enough protection. Other transactions can update or delete the same rows you just queried. InnoDB supports two types of ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-migration.html
This section describes techniques for moving or copying some or all InnoDB tables to a different server or instance. For example, you might move an entire MySQL instance to a larger, faster server; you might clone an entire MySQL instance to a new ...