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-deadlock-detection.html
When deadlock detection is enabled (the default), InnoDB automatically detects transaction deadlocks and rolls back a transaction or transactions to break the deadlock. InnoDB tries to pick small transactions to roll back, where the size of a ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-deadlock-example.html
The following example illustrates how an error can occur when a lock request causes a deadlock. Client A enables innodb_print_all_deadlocks, creates two tables, 'Animals' and 'Birds', and inserts data into each. Thererfore, the previous read-only ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-disabling-tablespace-path-validation.html
At startup, InnoDB scans directories defined by the innodb_directories variable for tablespace files. The paths of discovered tablespace files are validated against the paths recorded in the data dictionary. If the paths do not match, the paths in ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-doublewrite-buffer.html
The doublewrite buffer is a storage area where InnoDB writes pages flushed from the buffer pool before writing the pages to their proper positions in the InnoDB data files. If there is an operating system, storage subsystem, or unexpected mysqld ...
https://dev.mysql.com/doc/refman/9.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/9.7/en/innodb-file-defragmenting.html
Random insertions into or deletions from a secondary index can cause the index to become fragmented. Fragmentation means that the physical ordering of the index pages on the disk is not close to the index ordering of the records on the pages, or ...
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 ...