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/installation-layouts.html
Section 2.3.1, “MySQL Installation Layout on Microsoft Windows” Section 2.8.3, “MySQL Layout for Source Installation” Table 2.3, “MySQL Installation Layout for Generic Unix/Linux Binary Package” Table 2.12, “MySQL Installation Layout ... The installation layout differs for different installation types (for example, native packages, binary tarballs, and source tarballs), which can lead to confusion when managing different systems or using different installation ...
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. Using the SET_VAR optimizer hint to update the value of optimizer_switch temporarily, you can enable invisible indexes for the duration of a single query only, ...The feature applies to indexes other than primary keys (either explicit or ...
https://dev.mysql.com/doc/refman/8.0/en/keyring-key-types.html
MySQL Keyring supports keys of different types (encryption algorithms) and lengths: The available key types depend on which keyring plugin is installed. The permitted key lengths are subject to multiple factors: General keyring loadable-function ...
https://dev.mysql.com/doc/refman/8.0/en/large-page-support.html
In MySQL, large pages can be used by InnoDB, to allocate memory for its buffer pool and additional memory pool. Standard use of large pages in MySQL attempts to use the largest size supported, up to 4MB. MySQL also supports the Linux implementation ... Some hardware and operating system architectures support memory pages greater than the default (usually ...
https://dev.mysql.com/doc/refman/8.0/en/log-destinations.html
MySQL Server provides flexible control over the destination of output written to the general query log and the slow query log, if those logs are enabled. Possible destinations for log entries are log files or the general_log and slow_log tables in ...Setting this variable does not in itself enable the logs; they must be enabled ...
https://dev.mysql.com/doc/refman/8.0/en/metadata-locking.html
MySQL uses metadata locking to manage concurrent access to database objects and to ensure data consistency. As of MySQL 8.0.13, for XA transactions in PREPARED state, metadata locks are maintained across client disconnects and server restarts, ...
https://dev.mysql.com/doc/refman/8.0/en/mysqlbinlog-backup.html
By default, mysqlbinlog reads binary log files and displays their contents in text format. This enables you to examine events within the files more easily and to re-execute them (for example, by using the output as input to mysql). mysqlbinlog can ...This capability enables you to easily back up a binary log in its original ...
https://dev.mysql.com/doc/refman/8.0/en/out-of-memory.html
This causes it to use the mysql_use_result() C API function to retrieve the result set, which places less of a load on the client (but more on the server). Is it reasonable that it should return so many rows? If not, correct the query and try again.
https://dev.mysql.com/doc/refman/8.0/en/partitioning-info.html
From MySQL 8.0.16, when insertions, deletions, or updates are made to partitioned tables, the binary log records information about the partition and (if any) the subpartition in which the row event took place. The partition information is displayed ... This section discusses obtaining information about existing partitions, which can be done in a number of ...
https://dev.mysql.com/doc/refman/8.0/en/partitioning-key.html
Partitioning by key is similar to partitioning by hash, except that where hash partitioning employs a user-defined expression, the hashing function for key partitioning is supplied by the MySQL server. Note Tables using the NDB storage engine are ...NDB Cluster uses MD5() for this purpose; for tables using other storage engines, the server employs its own internal hashing ...