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-file-format-compatibility.html
This section describes these checks, how you can control them, and error and warning conditions that might arise. This mechanism lets you take advantage of some new features of an InnoDB release (such as performance improvements and bug fixes), and ... InnoDB incorporates several checks to guard against the possible crashes and data corruptions that might occur if you run an old release of the MySQL server on InnoDB data files that use a newer file ...
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. For example, you might hit this limit with a column prefix index of more than 255 characters on a TEXT or VARCHAR column, ...A ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-ddl.html
If this option is set to a value greater than 1, use READ UNCOMMITTED queries to find rows that were just inserted. If this option is set to a value greater than 1, changes made to the table using SQL are not immediately visible to memcached ... You ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-replication.html
The primary advantage of this configuration is increased write throughput on the source. 2013-09-24T13:04:38.639684Z 49 [Note] Slave I/O thread: connected to master 'root@localhost:13000', replication started in log '0.000001' at position 114 ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-multi-versioning.html
This information is stored in the system tablespace or undo tablespaces in a data structure called a rollback segment. You can use this information to calculate the space needed for your rollback segment. This removal operation is called a purge, ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-performance-read_ahead.html
Before this parameter was added, InnoDB would only calculate whether to issue an asynchronous prefetch request for the entire next extent when it read the last page of the current extent. You can set the value of this parameter in the MySQL ... A ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-preload-buffer-pool.html
For information about buffer pool dump and load procedures used in this example, see Section 14.8.3.6, “Saving and Restoring the Buffer Pool State”. In this case, you can check the events_stages_history table to view data for the completed event. In this case, the stage/innodb/buffer pool load instrument and related consumers must be enabled at ... To reduce the warmup period after restarting the server, InnoDB saves a percentage of the ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-read-only-instance.html
This option specifies the path, file name, and file size for InnoDB temporary tablespace data files. For example: --innodb-temp-data-file-path=../../../tmp/ibtmp1:12M:autoextend Usage Scenarios This mode of operation is appropriate in situations ...
https://dev.mysql.com/doc/refman/5.7/en/insert-optimization.html
This is considerably faster (many times faster in some cases) than using separate single-row INSERT statements. This reduces the parsing that MySQL must do and improves the insert speed. To optimize insert speed, combine many small operations into ...
https://dev.mysql.com/doc/refman/5.7/en/insert-select.html
This means that, when using replication, there is no guarantee that such a SELECT returns rows in the same order on the source and the replica, which can lead to inconsistencies between them. (This does not occur with tables using storage engines ...