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/procedure-analyse.html
This can be helpful for checking your existing tables, or after importing new data. ANALYSE([max_elements[,max_memory]]) Note PROCEDURE ANALYSE() is deprecated as of MySQL 5.7.18, and is removed in MySQL 8.0. ANALYSE() examines the result from a ...
https://dev.mysql.com/doc/refman/5.7/en/replace-third-party-yum.html
Important If you have chosen to replace your third-party MySQL distribution with a newer version of MySQL from the MySQL Yum repository, remember to run mysql_upgrade after the server starts, to check and possibly resolve any incompatibilities ...
https://dev.mysql.com/doc/refman/5.7/en/replica-logs-status.html
Important Do not attempt to update or insert rows in the mysql.slave_master_info or mysql.slave_relay_log_info tables manually. A replica server creates two replication metadata repositories, the connection metadata repository and the applier ...
https://dev.mysql.com/doc/refman/5.7/en/replication-administration-skip.html
When you use these methods, it is important to understand that you are not necessarily skipping a complete transaction, as is always the case with the GTID-based method described previously. If replication stops due to an issue with an event in a ...
https://dev.mysql.com/doc/refman/5.7/en/replication-compatibility.html
Important It is strongly recommended to use the most recent release available within a given MySQL release series because replication (and other) capabilities are continually being improved. MySQL supports replication from one release series to the ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-variables.html
sql_mode is also replicated except for the NO_DIR_IN_CREATE mode; the replica always preserves its own value for NO_DIR_IN_CREATE, regardless of changes to it on the source. However, when mysqlbinlog parses a SET @@sql_mode = mode statement, the ...
https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-lifecycle.html
It is important to note that the replica sets gtid_next in a session context. The life cycle of a GTID consists of the following steps: A transaction is executed and committed on the replication source server. This client transaction is assigned a ...
https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-restrictions.html
It is possible to import a dump made using mysqldump into a MySQL server running with GTID mode enabled, provided that there are no GTIDs in the target server's binary log. Because GTID-based replication is dependent on transactions, some features ...
https://dev.mysql.com/doc/refman/5.7/en/replication-howto-additionalslaves.html
Important Before copying, verify that all the files relating to the existing replica actually are stored in the data directory. You can add another replica to an existing replication configuration without stopping the source server. To do this, you ...
https://dev.mysql.com/doc/refman/5.7/en/replication-options-gtids.html
Important GTIDs are only available on a server instance up to the number of non-negative values for a signed 64-bit integer (2 to the power of 63, minus 1). The MySQL Server system variables described in this section are used to monitor and control ...