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/partitioning-overview.html
In MySQL, the InnoDB storage engine has long supported the notion of a tablespace, and the MySQL Server, even prior to the introduction of partitioning, could be configured to employ different physical directories for storing different databases ...
https://dev.mysql.com/doc/refman/5.7/en/partitioning.html
Note As of MySQL 5.7.17, the generic partitioning handler in the MySQL server is deprecated, and is removed in MySQL 8.0, when the storage engine used for a given table is expected to provide its own (“native”) partitioning handler. Use of ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-instrumentation-checking.html
It is always possible to determine what instruments the Performance Schema includes by checking the setup_instruments table. Changes to this code occur often, which also affects the set of instruments. It is not practical to list all the ...
https://dev.mysql.com/doc/refman/5.7/en/plugin-loading.html
In the descriptions, plugin_name stands for a plugin name such as innodb, csv, or validate_password. It is possible to control activation state for such a plugin using a --plugin_name[=activation_state] startup option, where plugin_name is the name ... Server plugins must be loaded into the server before they can be ...
https://dev.mysql.com/doc/refman/5.7/en/select-optimization.html
Both InnoDB and MyISAM have sets of guidelines for enabling and sustaining high performance in queries. For details, see Section 8.5.6, “Optimizing InnoDB Queries” and Section 8.6.1, “Optimizing MyISAM Queries”. You can optimize single-query ... Queries, in the form of SELECT statements, perform all the lookup operations in the ...
https://dev.mysql.com/doc/refman/5.7/en/storage-engine-setting.html
When you create a new table, you can specify which storage engine to use by adding an ENGINE table option to the CREATE TABLE statement: -- ENGINE=INNODB not needed unless you have set a different -- default storage engine. CREATE TABLE t1 (i INT) ...CREATE TABLE t2 (i INT) ENGINE = CSV; CREATE TABLE t3 (i INT) ENGINE = MEMORY; When you omit the ENGINE option, the default storage engine is ...
https://dev.mysql.com/doc/refman/5.7/en/truncate-table.html
Thus, it cannot be rolled back, it does not cause ON DELETE triggers to fire, and it cannot be performed for InnoDB tables with parent-child foreign key relationships. TRUNCATE TABLE fails for an InnoDB table or NDB table if there are any FOREIGN ...
https://dev.mysql.com/doc/refman/5.7/en/backup-policy.html
For example, MySQL Enterprise Backup can perform a physical backup of an entire instance, with optimizations to minimize overhead and avoid disruption when backing up InnoDB data files; mysqldump provides online logical backup. It was assumed ...A ...
https://dev.mysql.com/doc/refman/5.7/en/charset-unicode-conversion.html
InnoDB has a maximum index length of 767 bytes for tables that use COMPACT or REDUNDANT row format, so for utf8mb3 or utf8mb4 columns, you can index a maximum of 255 or 191 characters, respectively. Creating such tables also requires the option ...
https://dev.mysql.com/doc/refman/5.7/en/cost-model.html
The server recognizes these cost_name values for the server_cost table: disk_temptable_create_cost (default 40.0), disk_temptable_row_cost (default 1.0) The cost estimates for internally created temporary tables stored in a disk-based storage engine ... To generate execution plans, the optimizer uses a cost model that is based on estimates of the cost of various operations that occur during query ...