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-data-dictionary.html
For historical reasons, data dictionary metadata overlaps to some degree with information stored in InnoDB table metadata files (.frm files). The InnoDB data dictionary is comprised of internal system tables that contain metadata used to keep track ...
https://dev.mysql.com/doc/refman/5.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/5.7/en/innodb-monitor-types.html
There are two types of InnoDB monitor: The standard InnoDB Monitor displays the following types of information: Work done by the main background thread Semaphore waits Data about the most recent foreign key and deadlock errors Lock waits for ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-monitors.html
InnoDB monitors provide information about the InnoDB internal state. This information is useful for performance tuning. ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-performance-buffer-pool.html
This section provides configuration and tuning information for the InnoDB buffer pool.
https://dev.mysql.com/doc/refman/5.7/en/innodb-redo-log-buffer.html
A large log buffer enables large transactions to run without the need to write redo log data to disk before the transactions commit. For related information, see Memory Configuration, and Section 8.5.4, “Optimizing InnoDB Redo Logging”. The log ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-truncate-table-reclaim-space.html
For a table to be stored in its own .ibd file, innodb_file_per_table must enabled when the table is created. Additionally, there cannot be a foreign key constraint between the table being truncated and other tables, otherwise the TRUNCATE TABLE ...
https://dev.mysql.com/doc/refman/5.7/en/iterate.html
ITERATE means “start the loop again.” For an example, see Section 13.6.5.5, “LOOP Statement”. ITERATE label ITERATE can appear only within LOOP, REPEAT, and WHILE statements.
https://dev.mysql.com/doc/refman/5.7/en/linux-installation-juju.html
The Juju deployment framework supports easy installation and configuration of MySQL servers.
https://dev.mysql.com/doc/refman/5.7/en/myisam-optimization.html
myisamchk has a number of other options that you can use to improve the performance of a table: --analyze or -a: Perform key distribution analysis. This improves join performance by enabling the join optimizer to better choose the order in which to ... To coalesce fragmented rows and eliminate wasted space that results from deleting or updating rows, run myisamchk in recovery mode: $> myisamchk -r tbl_name You can optimize a table in the same way by using the OPTIMIZE TABLE SQL ...