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-compression-syntax-warnings.html
This section describes syntax warnings and errors that you may encounter when using the table compression feature with file-per-table tablespaces and general tablespaces. SQL Compression Syntax Warnings and Errors for File-Per-Table Tablespaces ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-compression-usage.html
This setting may still be useful for tables with many long BLOB, VARCHAR or TEXT columns, because such values often do compress well, and might therefore require fewer overflow pages as described in Section 14.9.1.5, “How Compression Works for ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-data-dictionary.html
The InnoDB data dictionary is comprised of internal system tables that contain metadata used to keep track of objects such as tables, indexes, and table columns. For historical reasons, data dictionary metadata overlaps to some degree with ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-deadlocks.html
FOR UPDATE) in each transaction; create indexes on the columns used in SELECT ... A deadlock is a situation in which multiple transactions are unable to proceed because each transaction holds a lock that is needed by another one. Because all ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-error-handling.html
During implicit rollbacks, as well as during the execution of an explicit ROLLBACK SQL statement, SHOW PROCESSLIST displays Rolling back in the State column for the relevant connection. InnoDB sometimes rolls back only the statement that failed, ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-file-format.html
The features associated with COMPRESSED and DYNAMIC row formats include compressed tables, efficient storage of off-page columns, and index key prefixes up to 3072 bytes (innodb_large_prefix). As InnoDB evolves, data file formats that are not ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-information-schema-examples-compression-sect.html
Compressing or uncompressing pages has consumed less than a second since the time the statistics were reset, because the columns COMPRESS_TIME and UNCOMPRESS_TIME are zero. Example 14.1 Using the Compression Information Schema Tables The following ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-information-schema-examples.html
Identifying Blocking Transactions It is sometimes helpful to identify which transaction blocks another. The tables that contain information about InnoDB transactions and data locks enable you to determine which transaction is waiting for another, ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-information-schema-fulltext_index-tables.html
The VALUE column is empty if there is no user-defined stopword table. INNODB_FT_BEING_DELETED: Provides a snapshot of the INNODB_FT_DELETED table; it is used only during an OPTIMIZE TABLE maintenance operation. When OPTIMIZE TABLE is run, the ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-information-schema-innodb_cmp.html
The INNODB_CMP and INNODB_CMP_RESET tables provide status information about operations related to compressed tables, which are described in Section 14.9, “InnoDB Table and Page Compression”. These two tables have identical contents, but reading ...