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-and-mysql-replication.html
To make a new replica without taking down the source or an existing replica, use the MySQL Enterprise Backup product. 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 ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-auto-increment-handling.html
innodb_autoinc_lock_mode = 0 (“traditional” lock mode) The traditional lock mode provides the same behavior that existed before the innodb_autoinc_lock_mode variable was introduced. InnoDB provides a configurable locking mechanism that can ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-change-buffer.html
Changing the setting affects the buffering of new operations; the merging of existing buffered entries is not affected. The change buffer is a special data structure that caches changes to secondary index pages when those pages are not in the ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-compression-syntax-warnings.html
To import the dump file into a new database, and have the tables re-created as they exist in the original database, ensure the server has the proper settings for the configuration parameters innodb_file_format and innodb_file_per_table. This ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-compression-tuning-monitoring.html
Increasing the size of the buffer pool might also help performance, so that more uncompressed pages can stay in memory, reducing the need to uncompress pages that exist in memory only in compressed form. Overall application performance, CPU and I/O ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-file-format-compatibility.html
The easiest way to determine the file format of an existing InnoDB tablespace is to examine the properties of the table it contains, using the SHOW TABLE STATUS command or querying the table INFORMATION_SCHEMA.TABLES. InnoDB incorporates several ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-fulltext-index.html
A full-text index is defined as part of a CREATE TABLE statement or added to an existing table using ALTER TABLE or CREATE INDEX. Full-text indexes are created on text-based columns (CHAR, VARCHAR, or TEXT columns) to speed up queries and DML ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-locks-set.html
Consistent reads ignore any locks set on the records that exist in the read view. A locking read, an UPDATE, or a DELETE generally set record locks on every index record that is scanned in the processing of an SQL statement. It does not matter ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-benefits.html
You can create a new table for data, or use existing tables. The combination of InnoDB tables and memcached offers advantages over using either by themselves. Direct access to the InnoDB storage engine avoids the parsing and planning overhead of SQL. Running memcached in the same process space as the MySQL server avoids the network overhead of passing requests back and ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-troubleshoot.html
This problem could also occur if you change an existing entry in the innodb_memcache.containers table without restarting the MySQL server afterward. This section describes issues that you may encounter when using the InnoDB memcached plugin. If you ...