PDF (US Ltr)
- 43.2Mb
PDF (A4)
- 43.3Mb
Man Pages (TGZ)
- 295.2Kb
Man Pages (Zip)
- 400.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/index-statistics.html
Storage engines collect statistics about tables for use by the optimizer. Table statistics are based on value groups, where a value group is a set of rows with the same key prefix value. For optimizer purposes, an important statistic is the average ...
https://dev.mysql.com/doc/refman/8.0/en/information-schema-introduction.html
INFORMATION_SCHEMA provides access to database metadata, information about the MySQL server such as the name of a database or table, the data type of a column, or access privileges. Other terms that are sometimes used for this information are data ...
https://dev.mysql.com/doc/refman/8.0/en/information-schema-table-reference.html
The following table summarizes all available INFORMATION_SCHEMA tables. For greater detail, see the individual table descriptions. Table 28.1 INFORMATION_SCHEMA Tables Table Name Description Deprecated ADMINISTRABLE_ROLE_AUTHORIZATIONS Grantable ...
https://dev.mysql.com/doc/refman/8.0/en/information-schema-tp-thread-state-table.html
Note As of MySQL 8.0.14, the thread pool INFORMATION_SCHEMA tables are also available as Performance Schema tables. (See Section 29.12.16, “Performance Schema Thread Pool Tables”.) The INFORMATION_SCHEMA tables are deprecated; expect them to be ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-data-encryption.html
InnoDB supports data-at-rest encryption for file-per-table tablespaces, general tablespaces, the mysql system tablespace, redo logs, and undo logs. As of MySQL 8.0.16, setting an encryption default for schemas and general tablespaces is also ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-error-handling.html
InnoDB sometimes rolls back only the statement that failed, other times it rolls back the entire transaction. If you run out of file space in a tablespace, a MySQL Table is full error occurs and InnoDB rolls back the SQL statement. A transaction ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-locking-reads.html
If you query data and then insert or update related data within the same transaction, the regular SELECT statement does not give enough protection. Other transactions can update or delete the same rows you just queried. InnoDB supports two types of ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-memcached-intro.html
The InnoDB memcached plugin implements memcached as a MySQL plugin daemon that accesses the InnoDB storage engine directly, bypassing the MySQL SQL layer. The following diagram illustrates how an application accesses data through the ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-memcached-security.html
Caution Consult this section before deploying the daemon_memcached plugin on a production server, or even on a test server if the MySQL instance contains sensitive data. Because memcached does not use an authentication mechanism by default, and the ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-multiple-buffer-pools.html
For systems with buffer pools in the multi-gigabyte range, dividing the buffer pool into separate instances can improve concurrency, by reducing contention as different threads read and write to cached pages. This feature is typically intended for ...