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-consistent-read.html
A consistent read means that InnoDB uses multi-versioning to present to a query a snapshot of the database at a point in time. The query sees the changes made by transactions that committed before that point in time, and no changes made by later or ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-deadlocks-handling.html
Another way to serialize transactions is to create an auxiliary “semaphore” table that contains just a single row. This section builds on the conceptual information about deadlocks in Section 14.7.5.2, “Deadlock Detection”. It explains how ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-disk-io.html
InnoDB uses asynchronous disk I/O where possible, by creating a number of threads to handle I/O operations, while permitting other database operations to proceed while the I/O is still in progress. On Linux and Windows platforms, InnoDB uses the ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-enabling-monitors.html
When this option is used, InnoDB creates a file named innodb_status.pid in the data directory and writes output to it every 15 seconds, approximately. When InnoDB monitors are enabled for periodic output, InnoDB writes the output to mysqld server ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-file-format.html
The following file format configuration parameters are deprecated in and may be removed in a future release: innodb_file_format innodb_file_format_check innodb_file_format_max innodb_large_prefix The file format configuration parameters were ... As ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-limits.html
If you reduce the InnoDB page size to 8KB or 4KB by specifying the innodb_page_size option when creating the MySQL instance, the maximum length of the index key is lowered proportionally, based on the limit of 3072 bytes for a 16KB page size. This ...
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
These limits primarily apply if you intend to create an index on a value column to run report-generating queries on that column using SQL. This section describes issues that you may encounter when using the InnoDB memcached plugin. If you encounter ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-txn.html
This option is less appropriate when accessing the same tables through both memcached and SQL, because it blocks CREATE INDEX statements on the tables, which could be important for running reporting queries. Unlike traditional memcached, the ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-online-ddl-single-multi.html
Before the introduction of online DDL, it was common practice to combine many DDL operations into a single ALTER TABLE statement. Because each ALTER TABLE statement involved copying and rebuilding the table, it was more efficient to make several ...