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-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 ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-performance-read_ahead.html
A read-ahead request is an I/O request to prefetch multiple pages in the buffer pool asynchronously, in anticipation that these pages are needed soon. InnoDB uses two read-ahead algorithms to improve I/O performance: Linear read-ahead is a ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-redo-log-buffer.html
The log buffer is the memory area that holds data to be written to the log files on disk. The contents of the log buffer are periodically flushed to disk. A large log buffer enables large transactions to run without the need to write redo log data ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-model.html
The InnoDB transaction model aims combine the best properties of a multi-versioning database with traditional two-phase locking. InnoDB performs locking at the row level and runs queries as nonlocking consistent reads by default, in the style of ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html
The following general guidelines apply to troubleshooting InnoDB problems: When an operation fails or you suspect a bug, look at the MySQL server error log (see Section 5.4.2, “The Error Log”). Server Error Message Reference provides ...
https://dev.mysql.com/doc/refman/5.7/en/insert-delayed.html
The DELAYED option for the INSERT statement is a MySQL extension to standard SQL. The server recognizes but ignores the DELAYED keyword, handles the insert as a nondelayed insert, and generates an ER_WARN_LEGACY_SYNTAX_CONVERTED warning: INSERT ...