PDF (US Ltr)
- 35.0Mb
PDF (A4)
- 35.1Mb
Man Pages (TGZ)
- 255.5Kb
Man Pages (Zip)
- 360.4Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/information-schema-innodb-cmp-per-index-table.html
The INNODB_CMP_PER_INDEX and INNODB_CMP_PER_INDEX_RESET tables provide status information on operations related to compressed InnoDB tables and indexes, with separate statistics for each combination of database, table, and index, to help you ...
https://dev.mysql.com/doc/refman/5.7/en/information-schema-innodb-sys-indexes-table.html
The INNODB_SYS_INDEXES table provides metadata about InnoDB indexes, equivalent to the information in the internal SYS_INDEXES table in the InnoDB data dictionary. For related usage information and examples, see Section 14.16.3, “InnoDB ...
https://dev.mysql.com/doc/refman/5.7/en/information-schema-optimizer-trace-table.html
The OPTIMIZER_TRACE table provides information produced by the optimizer tracing capability for traced statements. The OPTIMIZER_TRACE table has these columns: QUERY The text of the traced statement. MISSING_BYTES_BEYOND_MAX_MEM_SIZE Each ...
https://dev.mysql.com/doc/refman/5.7/en/information-schema-partitions-table.html
Each row in this table corresponds to an individual partition or subpartition of a partitioned table. The PARTITIONS table has these columns: TABLE_CATALOG The name of the catalog to which the table belongs. TABLE_SCHEMA The name of the schema ...
https://dev.mysql.com/doc/refman/5.7/en/information-schema-profiling-table.html
Its contents correspond to the information produced by the SHOW PROFILE and SHOW PROFILES statements (see Section 13.7.5.30, “SHOW PROFILE Statement”). The table is empty unless the profiling session variable is set to 1. Note This table is ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-compression-tuning-monitoring.html
Overall application performance, CPU and I/O utilization and the size of disk files are good indicators of how effective compression is for your application. This section builds on the performance tuning advice from Section 14.9.1.3, “Tuning ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-create-table-external.html
There are different reasons for creating InnoDB tables externally; that is, creating tables outside of the data directory. Those reasons might include space management, I/O optimization, or placing tables on a storage device with particular ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-deadlocks-handling.html
This section builds on the conceptual information about deadlocks in Section 14.7.5.2, “Deadlock Detection”. It explains how to organize database operations to minimize deadlocks and the subsequent error handling required in applications.
https://dev.mysql.com/doc/refman/5.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/5.7/en/innodb-index-types.html
Each InnoDB table has a special index called the clustered index that stores row data. To get the best performance from queries, inserts, and other database operations, it is important to understand how InnoDB uses the clustered index to optimize ...