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-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 ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-performance-optimizer-statistics.html
You can use the STATS_PERSISTENT, STATS_AUTO_RECALC, and STATS_SAMPLE_PAGES clauses with CREATE TABLE and ALTER TABLE statements to configure optimizer statistics for individual tables. This section describes how to configure persistent and ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-physical-structure.html
InnoDB performs a bulk load when creating or rebuilding B-tree indexes. This method of index creation is known as a sorted index build. With the exception of spatial indexes, InnoDB indexes are B-tree data structures. Spatial indexes use R-trees, ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-recovery.html
In some cases of database corruption, it is enough to dump, drop, and re-create one or a few corrupt tables. To achieve point-in-time recovery after restoring a backup, you can apply changes from the binary log that occurred after the backup was ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-redo-log.html
If InnoDB detects that the innodb_log_file_size differs from the redo log file size, it writes a log checkpoint, closes and removes the old log files, creates new log files at the requested size, and opens the new log files. The redo log is a ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-table-compression.html
Table compression is enabled using the ROW_FORMAT=COMPRESSED attribute with CREATE TABLE or ALTER TABLE. This section describes InnoDB table compression, which is supported with InnoDB tables that reside in file_per_table tablespaces or general ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html
Issues relating to the InnoDB data dictionary include failed CREATE TABLE statements (orphan table files), inability to open InnoDB files, and system cannot find the path specified errors. If the problem is with table creation, tablespaces, or data ... The following general guidelines apply to troubleshooting InnoDB problems: When an operation fails or you suspect a bug, look at the MySQL server error log (see Section 5.4.2, “The Error ...
https://dev.mysql.com/doc/refman/5.7/en/key-space.html
In MyISAM tables, you can also prefix compress numbers by specifying the PACK_KEYS=1 table option when you create the table. You can roughly calculate the size for the index file as (key_length+4)/0.67, summed over all keys. This is for the worst ...
https://dev.mysql.com/doc/refman/5.7/en/keyring-file-plugin.html
The keyring_file keyring plugin stores keyring data in a file local to the server host. Warning For encryption key management, the keyring_file plugin is not intended as a regulatory compliance solution. Security standards such as PCI, FIPS, and ...