PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 297.2Kb
Man Pages (Zip)
- 402.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/innodb-adaptive-hash.html
Based on the observed pattern of searches, a hash index is built using a prefix of the index key. The adaptive hash index enables InnoDB to perform more like an in-memory database on systems with appropriate combinations of workload and sufficient ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-backup.html
The key to safe database management is making regular backups. Hot and cold backups are physical backups that copy actual data files, which can be used directly by the mysqld server for faster restore. Using MySQL Enterprise Backup is the ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-compression-background.html
The compressed page size is specified through the CREATE TABLE or ALTER TABLE KEY_BLOCK_SIZE parameter. The level of compression is the same regardless of the KEY_BLOCK_SIZE value. As you specify smaller values for KEY_BLOCK_SIZE, you get the I/O ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-compression-tuning-monitoring.html
The INNODB_CMP table reports information about compression activity for each compressed page size (KEY_BLOCK_SIZE) in use. The key statistics to consider are the number of, and amount of time spent performing, compression and uncompression ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-error-handling.html
A duplicate-key error rolls back the SQL statement, if you have not specified the IGNORE option in your statement. InnoDB sometimes rolls back only the statement that failed, other times it rolls back the entire transaction. If you run out of file ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-init-startup-configuration.html
For example, if you use MyISAM tables, consider the amount of memory allocated for the key buffer (key_buffer_size). innodb_buffer_pool_size + key_buffer_size + max_connections*(sort_buffer_size+read_buffer_size+binlog_cache_size) + ... The first ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-locking-transaction-model.html
Section 17.7.4, “Phantom Rows” describes how InnoDB uses next-key locking to avoid phantom rows. To implement a large-scale, busy, or highly reliable database application, to port substantial code from a different database system, or to tune ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-memcached-txn.html
With the caching setting, if memcached cannot find a key in memory, it searches for the value in an InnoDB table. Unlike traditional memcached, the daemon_memcached plugin allows you to control durability of data values produced through calls to ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-memcached.html
The InnoDB memcached plugin (daemon_memcached) provides an integrated memcached daemon that automatically stores and retrieves data from InnoDB tables, turning the MySQL server into a fast “key-value store”. Important The InnoDB memcached ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-migration.html
IMPORT TABLESPACE feature does not enforce foreign key constraints on imported data. This section describes techniques for moving or copying some or all InnoDB tables to a different server or instance. For example, you might move an entire MySQL ...