PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 255.8Kb
Man Pages (Zip)
- 360.7Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/group-replication-usage-advice-and-limitations-of-distributed-recovery.html
It is based on classic asynchronous replication and as such it may be slow if the server joining the group is not provisioned at all or is provisioned with a very old backup image. This means that if the data to transfer is too big at phase 1, the ...
https://dev.mysql.com/doc/refman/5.7/en/identifier-case-sensitivity.html
In MySQL, databases correspond to directories within the data directory. Each table within a database corresponds to at least one file within the database directory (and possibly more, depending on the storage engine). Consequently, the case ...
https://dev.mysql.com/doc/refman/5.7/en/index-hints.html
Index hints give the optimizer information about how to choose indexes during query processing. Index hints, described here, differ from optimizer hints, described in Section 8.9.3, “Optimizer Hints”. They also work with multi-table DELETE ...
https://dev.mysql.com/doc/refman/5.7/en/information-schema-ndb-transid-mysql-connection-map-table.html
The ndb_transid_mysql_connection_map table provides a mapping between NDB transactions, NDB transaction coordinators, and MySQL Servers attached to an NDB Cluster as API nodes. This information is used when populating the server_operations and ...
https://dev.mysql.com/doc/refman/5.7/en/information-schema-tp-thread-group-stats-table.html
The TP_THREAD_GROUP_STATS table has these columns: TP_GROUP_ID The thread group ID. This number is incremented when a statement starts executing, not when it finishes. QUERIES_QUEUED The number of statements received that were queued for execution.
https://dev.mysql.com/doc/refman/5.7/en/innodb-compression-tuning.html
Most often, the internal optimizations described in InnoDB Data Storage and Compression ensure that the system runs well with compressed data. However, because the efficiency of compression depends on the nature of your data, you can make decisions ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-file-per-table-tablespaces.html
A file-per-table tablespace contains data and indexes for a single InnoDB table, and is stored on the file system in a single data file. File-per-table tablespace characteristics are described under the following topics in this section: ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-information-schema-system-tables.html
You can extract metadata about schema objects managed by InnoDB using InnoDB INFORMATION_SCHEMA system tables. This information comes from the InnoDB internal system tables (also referred to as the InnoDB data dictionary), which cannot be queried ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-init-startup-configuration.html
innodb_buffer_pool_size + key_buffer_size + max_connections*(sort_buffer_size+read_buffer_size+binlog_cache_size) + max_connections*2MB Each thread uses a stack (often 2MB, but only 256KB in MySQL binaries provided by Oracle Corporation.) and in the ... The first decisions to make about InnoDB configuration involve the configuration of data files, log files, page size, and memory buffers, which should be configured before initializing ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-locks-set.html
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 statement. It does not matter whether there are WHERE conditions in the statement that would exclude the row. InnoDB ...