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
The type of read varies for selects in clauses like INSERT INTO ... 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 ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-disk-io.html
Read-Ahead If InnoDB can determine there is a high probability that data might be needed soon, it performs read-ahead operations to bring that data into the buffer pool so that it is available in memory. In random read-ahead, if InnoDB notices that ... 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 ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-file-defragmenting.html
Random insertions into or deletions from a secondary index can cause the index to become fragmented. If the insertions into an index are always ascending and records are deleted only from the end, the InnoDB filespace management algorithm ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-information-schema-internal-data.html
The data exposed by the transaction and locking tables (INNODB_TRX, INNODB_LOCKS, and INNODB_LOCK_WAITS) represents a glimpse into fast-changing data. For performance reasons, and to minimize the chance of misleading joins between the transaction ...This is not like user tables, where the data changes only when application-initiated updates ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-information-schema-system-tables.html
As a final step, insert a row into table t1 (TABLE_ID = 71) and view the data in the INNODB_SYS_TABLESTATS table. mysql> INSERT INTO t1 VALUES(5, 'abc', 'def'); Query OK, 1 row affected (0.06 sec) mysql> SELECT * FROM ... You can extract metadata ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-dml.html
Single-row DML statements are the easiest types of statements to turn into memcached operations. Benchmarks suggest that the daemon_memcached plugin speeds up DML operations (inserts, updates, and deletes) more than it speeds up queries. Therefore, ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-internals.html
The following configuration options are supported by the config_options table: separator: Used to separate values of a long string into separate values when there are multiple value_columns defined. For example, if you define col1, col2 as value ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-troubleshoot.html
When defining your own InnoDB table for use with the daemon_memcached plugin, and columns in the table are defined as NOT NULL, ensure that values are supplied for the NOT NULL columns when inserting a record for the table into the ... This section ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-online-ddl-failure-conditions.html
For example, you might insert duplicate values into a column while a unique index is being created, or you might insert NULL values into a column while creating a primary key index on that column. The failure of an online DDL operation is typically ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-online-ddl-performance.html
In-place operations read less data into the buffer pool than the table-copy operations, which reduces purging of frequently accessed data from memory. Online DDL and Metadata Locks Online DDL operations can be viewed as having three phases: Phase 1: ... Online DDL improves several aspects of MySQL operation: Applications that access the table are more responsive because queries and DML operations on the table can proceed while the DDL operation is in ...