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/history.html
We started out with the intention of using the mSQL database system to connect to our tables using our own fast low-level (ISAM) routines. However, after some testing, we came to the conclusion that mSQL was not fast enough or flexible enough for ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-adaptive-hash.html
If a table fits almost entirely in main memory, a hash index speeds up queries by enabling direct lookup of any element, turning the index value into a sort of pointer. The adaptive hash index enables InnoDB to perform more like an in-memory ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-autocommit-commit-rollback.html
$> mysql test mysql> CREATE TABLE customer (a INT, b CHAR (20), INDEX (a)); Query OK, 0 rows affected (0.00 sec) mysql> -- Do a transaction with autocommit turned on. If autocommit mode is enabled, each SQL statement forms a single transaction on ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-check-availability.html
Issue the SHOW ENGINES statement to view the available MySQL storage engines.
https://dev.mysql.com/doc/refman/5.7/en/innodb-error-handling.html
If you run out of file space in a tablespace, a MySQL Table is full error occurs and InnoDB rolls back the SQL statement. InnoDB sometimes rolls back only the statement that failed, other times it rolls back the entire transaction. A transaction ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-tuning.html
For other ways to reduce or tune I/O for table operations, see Section 8.5.8, “Optimizing InnoDB Disk I/O”. Increase the setting when processing large numbers of updates intended only for statistical analysis, where losing the last N updates in ... Because using InnoDB in combination with memcached involves writing all data to disk, whether immediately or sometime later, raw performance is expected to be somewhat slower than using memcached by ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-monitor-types.html
There are two types of InnoDB monitor: The standard InnoDB Monitor displays the following types of information: Work done by the main background thread Semaphore waits Data about the most recent foreign key and deadlock errors Lock waits for ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-performance-use_sys_malloc.html
Most workloads, especially those where memory is frequently allocated and released (such as multi-table joins), benefit from using a more highly tuned memory allocator as opposed to the internal, InnoDB-specific memory allocator. When InnoDB was ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-read-only-instance.html
You can query InnoDB tables where the MySQL data directory is on read-only media by enabling the --innodb-read-only configuration option at server startup. This option specifies the path, file name, and file size for InnoDB temporary tablespace ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-redo-log.html
During normal operations, the redo log encodes requests to change table data that result from SQL statements or low-level API calls. The redo log is a disk-based data structure used during crash recovery to correct data written by incomplete ...