PDF (US Ltr)
- 35.0Mb
PDF (A4)
- 35.1Mb
Man Pages (TGZ)
- 255.5Kb
Man Pages (Zip)
- 360.3Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/innodb-and-mysql-replication.html
It is possible to use replication in a way where the storage engine on the replica is not the same as the storage engine on the source. For example, you can replicate modifications to an InnoDB table on the source to a MyISAM table on the replica.
https://dev.mysql.com/doc/refman/5.7/en/innodb-benchmarking.html
If InnoDB is not the default storage engine, you can determine if your database server and applications work correctly with InnoDB by restarting the server with --default-storage-engine=InnoDB on the command line or with ...
https://dev.mysql.com/doc/refman/5.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/5.7/en/innodb-information-schema-temp-table-info.html
INNODB_TEMP_TABLE_INFO provides information about user-created InnoDB temporary tables that are active in the InnoDB instance. It does not provide information about internal InnoDB temporary tables used by the optimizer. mysql> SHOW TABLES FROM ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-information-schema.html
This section provides information and usage examples for InnoDB INFORMATION_SCHEMA tables. InnoDB INFORMATION_SCHEMA tables provide metadata, status information, and statistics about various aspects of the InnoDB storage engine. You can view a list ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-limits.html
This section describes limits for InnoDB tables, indexes, tablespaces, and other aspects of the InnoDB storage engine. A table can contain a maximum of 1017 columns (raised in MySQL 5.6.9 from the earlier limit of 1000). If innodb_large_prefix is ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-porting-memcached.html
This is because InnoDB performs best for large-scale insertions if primary key values are added in sorted order (as they are with auto-increment values). Primary key values are included in secondary indexes, which takes up unnecessary space if the ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-online-ddl-failure-conditions.html
The failure of an online DDL operation is typically due to one of the following conditions: An ALGORITHM clause specifies an algorithm that is not compatible with the particular type of DDL operation or storage engine. A LOCK clause specifies a low ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-online-ddl-limitations.html
The following limitations apply to online DDL operations: The table is copied when creating an index on a TEMPORARY TABLE. The ALTER TABLE clause LOCK=NONE is not permitted if there are ON...CASCADE or ON...SET NULL constraints on the table. Before ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-performance-optimizer-statistics.html
This section describes how to configure persistent and non-persistent optimizer statistics for InnoDB tables. Persistent optimizer statistics are persisted across server restarts, allowing for greater plan stability and more consistent query ...