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/innodb-locks-set.html
If you have no indexes suitable for your statement and MySQL must scan the entire table to process the statement, every row of the table becomes locked, which in turn blocks all inserts by other users to the table. LOCK TABLES sets table locks, but ... A locking read, an UPDATE, or a DELETE generally set record locks on every index record that is scanned in the processing of an SQL ...
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. Figure 17.4 MySQL Server with Integrated memcached Server Features of the daemon_memcached ...
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 ...Do not allow memcached access to these servers from the Internet; only allow access from within a firewalled intranet, ideally from a subnet whose membership you can ...
https://dev.mysql.com/doc/refman/8.0/en/install-component.html
A component provides services that are available to the server and other components; see Section 7.5, “MySQL Components”. INSTALL COMPONENT requires the INSERT privilege for the mysql.component system table because it adds a row to that table to ...[SET variable = expr [, variable = expr] ...] variable: { {GLOBAL | @@GLOBAL.} [component_prefix.]system_var_name | {PERSIST | @@PERSIST.} [component_prefix.]system_var_name } This statement installs one or more components, which become active ...
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, ...