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-temporary-tablespace.html
InnoDB uses session temporary tablespaces and a global temporary tablespace. Session Temporary Tablespaces Session temporary tablespaces store user-created temporary tables and internal temporary tables created by the optimizer when InnoDB is ...
https://dev.mysql.com/doc/refman/8.0/en/invisible-indexes.html
MySQL supports invisible indexes; that is, indexes that are not used by the optimizer. The feature applies to indexes other than primary keys (either explicit or implicit). ALTER INDEX operation: ALTER TABLE t1 ALTER INDEX i_idx INVISIBLE; ALTER ...
https://dev.mysql.com/doc/refman/8.0/en/keyring-encrypted-file-component.html
Note component_keyring_encrypted_file is an extension included in MySQL Enterprise Edition, a commercial product. The component_keyring_encrypted_file keyring component stores keyring data in an encrypted, password-protected file local to the ...
https://dev.mysql.com/doc/refman/8.0/en/keyring-file-component.html
The component_keyring_file keyring component stores keyring data in a file local to the server host. Warning For encryption key management, the component_keyring_file and component_keyring_encrypted_file components are not intended as a regulatory ...
https://dev.mysql.com/doc/refman/8.0/en/keyring-hashicorp-plugin.html
Note The keyring_hashicorp plugin is an extension included in MySQL Enterprise Edition, a commercial product. The keyring_hashicorp keyring plugin communicates with HashiCorp Vault for back end storage. No key information is permanently stored in ...
https://dev.mysql.com/doc/refman/8.0/en/keyring-metadata.html
To see whether a keyring plugin is loaded, check the Information Schema PLUGINS table or use the SHOW PLUGINS statement (see Section 7.6.2, “Obtaining Server Plugin Information”). If the component loaded but failed to initialize, the value is ...
https://dev.mysql.com/doc/refman/8.0/en/memory-storage-engine.html
The MEMORY storage engine (formerly known as HEAP) creates special-purpose tables with contents that are stored in memory. Because the data is vulnerable to crashes, hardware issues, or power outages, only use these tables as temporary work areas ...
https://dev.mysql.com/doc/refman/8.0/en/merge-storage-engine.html
The MERGE storage engine, also known as the MRG_MyISAM engine, is a collection of identical MyISAM tables that can be used as one. “Identical” means that all tables have identical column data types and index information. You cannot merge MyISAM ...
https://dev.mysql.com/doc/refman/8.0/en/merge-table-problems.html
The following are known problems with MERGE tables: MERGE child tables are locked through the parent table. If the parent is a temporary table, it is not locked, and thus the child tables are also not locked; this means that parallel use of the ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndb-api-statistics.html
A number of types of statistical counters relating to actions performed by or affecting Ndb objects are available. Such actions include starting and closing (or aborting) transactions; primary key and unique key operations; table, range, and pruned ...