PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 256.4Kb
Man Pages (Zip)
- 361.3Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/optimizing-innodb-bulk-data-loading.html
SET unique_checks=1; For big tables, this saves a lot of disk I/O because InnoDB can use its change buffer to write secondary index records in a batch. SET foreign_key_checks=1; For big tables, this can save a lot of disk I/O. Use the multiple-row ... These performance tips supplement the general guidelines for fast inserts in Section 8.2.4.1, “Optimizing INSERT ...
https://dev.mysql.com/doc/refman/5.7/en/password-logging.html
For security reasons, this option is not recommended for production use. For security reasons, this file should be written to a directory accessible only to the MySQL server and users with a legitimate reason to view the log. In this case, the ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-socket-instances-table.html
Information available in this table provides a real-time snapshot of the active connections to the server. row *************************** EVENT_NAME: wait/io/socket/sql/server_tcpip_socket OBJECT_INSTANCE_BEGIN: 4316699040 THREAD_ID: 1 SOCKET_ID: ... The socket_instances table provides a real-time snapshot of the active connections to the MySQL ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-status-variable-tables.html
An application that wants only global values should use this table. An application that wants all status variable values for its own session should use this table. An application that wants to know the session variable values for specific sessions ... Note The value of the show_compatibility_56 system variable affects the information available from the tables described ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-transaction-tables.html
Use this instrument to enable or disable collection of individual transaction event classes. There are subtle implications to this approach: Transaction events in the Performance Schema do not fully include the statement events associated with the ...Within the event hierarchy, wait events nest within stage events, which nest within statement events, which nest within transaction ...
https://dev.mysql.com/doc/refman/5.7/en/pluggable-storage-common-layer.html
This is one of the reasons that MySQL has always been known to have such high performance, matching or beating proprietary monolithic databases in industry standard benchmarks. This area also includes support for capabilities such as multi-version ... A MySQL pluggable storage engine is the component in the MySQL database server that is responsible for performing the actual data I/O operations for a database as well as enabling and enforcing certain feature sets that target a specific application ...
https://dev.mysql.com/doc/refman/5.7/en/replace-third-party-yum.html
Note This step is not necessary for an installation that was configured with a Yum repository release package (like Percona) if you are going to remove the release package (percona-release.noarch for Percona), as shown in the uninstall command for ... For supported Yum-based platforms (see Section 2.5.1, “Installing MySQL on Linux Using the MySQL Yum Repository”, for a list), you can replace a third-party distribution of MySQL with the latest GA release (from the MySQL 5.7 series currently) from the MySQL Yum ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-transactions.html
When this variable is OFF (the default), logging is as just described. When this variable is ON, logging occurs immediately for nontransactional statements occurring anywhere in the transaction (not just initial nontransactional statements). In ...
https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-restrictions.html
This section provides information about restrictions on and limitations of replication with GTIDs. This restriction is due to the fact that updates to tables that use a nontransactional storage engine mixed with updates to tables that use a ...
https://dev.mysql.com/doc/refman/5.7/en/replication-howto-masterbaseconfig.html
This server ID is used to identify individual servers within the replication topology, and must be a positive integer between 1 and (232)−1. You can change the server_id value dynamically by issuing a statement like this: SET GLOBAL server_id = 2; ... To configure a source to use binary log file position based replication, you must ensure that binary logging is enabled, and establish a unique server ...