PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 297.2Kb
Man Pages (Zip)
- 402.5Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/estimating-performance.html
For small tables, you can usually find a row in one disk seek (because the index is probably cached). For bigger tables, you can estimate that, using B-tree indexes, you need this many seeks to find a row: log(row_count) / log(index_block_length / 3 ... In most cases, you can estimate query performance by counting disk ...
https://dev.mysql.com/doc/refman/8.0/en/faqs-general.html
For the syntax required to perform multiple-table updates, see Section 15.2.17, “UPDATE Statement”; for that required to perform multiple-table deletes, see Section 15.2.2, “DELETE Statement”. A multiple-table insert can be accomplished ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-memcached-intro.html
Direct access to InnoDB tables, bypassing the SQL parser, the optimizer, and even the Handler API layer. Although memcached has no concept of transactions, you can use this option to control how soon memcached sees changes caused by SQL statements ... The InnoDB memcached plugin implements memcached as a MySQL plugin daemon that accesses the InnoDB storage engine directly, bypassing the MySQL SQL ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-performance-midpoint_insertion.html
The goal is to make sure that frequently accessed (“hot”) pages remain in the buffer pool, even as read-ahead and full table scans bring in new blocks that might or might not be accessed afterward. You can control the insertion point in the LRU ... Rather than using a strict LRU algorithm, InnoDB uses a technique to minimize the amount of data that is brought into the buffer pool and never accessed ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-troubleshooting.html
If the problem is with table creation, tablespaces, or data dictionary operations, refer to the InnoDB Information Schema system tables to examine contents of the InnoDB internal data dictionary. The following general guidelines apply to ...
https://dev.mysql.com/doc/refman/8.0/en/install-component.html
INSTALL COMPONENT requires the INSERT privilege for the mysql.component system table because it adds a row to that table to register the component. Specifying PERSIST for any variable in SET silently executes SET PERSIST_ONLY immediately after ...
https://dev.mysql.com/doc/refman/8.0/en/keyring.html
Key metadata access: The Performance Schema keyring_keys table exposes metadata for keys in the keyring. The keyring_keys table does not expose any sensitive keyring data such as key contents. The Performance Schema keyring_component_status table ...
https://dev.mysql.com/doc/refman/8.0/en/ldml-rules.html
Orderings are given as a set of rules that begin with a reset rule that establishes an anchor point, followed by shift rules that indicate how characters sort relative to the anchor point. The following table shows the correspondence between ...This ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-limitations-resolved.html
These are described briefly in the following list: Database and table names. In NDB 7.6 and earlier, when using the NDB storage engine, the maximum allowed length both for database names and for table names was 63 bytes, and a statement using a ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-programs-ndb-top.html
This user must be able to read tables in the ndbinfo database (ndb_top uses information from ndbinfo.cpustat and related tables). The following table includes all options that are specific to the NDB Cluster program ndb_top. ndb_top displays ...