PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 297.2Kb
Man Pages (Zip)
- 402.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/information-schema-innodb-columns-table.html
For related usage information and examples, see Section 17.15.3, “InnoDB INFORMATION_SCHEMA Schema Object Tables”. The INNODB_COLUMNS table has these columns: TABLE_ID An identifier representing the table associated with the column; the same ...
https://dev.mysql.com/doc/refman/8.0/en/information-schema-statistics-table.html
The information_schema_stats_expiry system variable defines the period of time before cached table statistics expire. If there are no cached statistics or statistics have expired, statistics are retrieved from storage engines when querying table ...
https://dev.mysql.com/doc/refman/8.0/en/information-schema-tables-table.html
The information_schema_stats_expiry system variable defines the period of time before cached table statistics expire. If there are no cached statistics or statistics have expired, statistics are retrieved from storage engines when querying table ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-benefits.html
InnoDB tables have the following benefits: If the server unexpectedly exits because of a hardware or software issue, regardless of what was happening in the database at the time, you don't need to do anything special after restarting the database.
https://dev.mysql.com/doc/refman/8.0/en/innodb-compression-usage.html
Compressed tables can be created in file-per-table tablespaces or in general tablespaces. The system tablespace (space 0, the .ibdata files) can contain user-created tables, but it also contains internal system data, which is never compressed.
https://dev.mysql.com/doc/refman/8.0/en/innodb-file-space.html
The data files that you define in the configuration file using the innodb_data_file_path configuration option form the InnoDB system tablespace. You cannot define where within the system tablespace your tables are allocated. In a newly created ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-limits.html
This section describes limits for InnoDB tables, indexes, tablespaces, and other aspects of the InnoDB storage engine. The index key prefix length limit is 3072 bytes for InnoDB tables that use DYNAMIC or COMPRESSED row format. The index key prefix ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-memcached-developing.html
Typically, writing an application for the InnoDB memcached plugin involves some degree of rewriting or adapting existing code that uses MySQL or the memcached API. With the daemon_memcached plugin, instead of many traditional memcached servers ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-memcached-internals.html
InnoDB API for the InnoDB memcached Plugin The InnoDB memcached engine accesses InnoDB through InnoDB APIs, most of which are directly adopted from embedded InnoDB. InnoDB API functions are passed to the InnoDB memcached engine as callback ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-online-ddl-operations.html
Online support details, syntax examples, and usage notes for DDL operations are provided under the following topics in this section. Index Operations Primary Key Operations Column Operations Generated Column Operations Foreign Key Operations Table ...