PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 297.2Kb
Man Pages (Zip)
- 402.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/replication-bugs.html
If you have a “phantom” problem (one that you cannot duplicate at will), use the following procedure: Verify that no user error is involved. When you have determined that there is no user error involved, and replication still either does not ...
https://dev.mysql.com/doc/refman/8.0/en/replication-encrypted-connections.html
The connection procedure negotiates the use of the highest TLS version that both the source and the replica permit. To use an encrypted connection for the transfer of the binary log required during replication, both the source and the replica ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-current-user.html
In some cases, such as statements that change passwords, the function reference is expanded before it is written to the binary log, so that the statement includes the user name. For all other cases, the name of the current user on the source is ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-drop-if-exists.html
IF EXISTS statements for stored programs (stored procedures and functions, triggers, and events) are also replicated, even if the stored program to be dropped does not exist on the source. The DROP DATABASE IF EXISTS, DROP TABLE IF EXISTS, and DROP ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-triggers.html
If the trigger needs multiple result values from the code, you can put the code in a stored procedure and return the values using OUT parameters. With statement-based replication, triggers executed on the source also execute on the replica. With ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-functions.html
The procedure used is to back up server2 using mysqldump, then to restore this backup on server1. This section provides examples of stored functions (see Chapter 27, Stored Objects) which you can create using some of the built-in functions provided ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-howto.html
This is a “cold start” procedure that assumes either that you are starting the source server for the first time, or that it is possible to stop it; for information about provisioning replicas using GTIDs from a running source server, see Section ... This section describes a process for configuring and starting GTID-based replication in MySQL ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids.html
A general procedure for setting up and starting GTID-based replication (see Section 19.1.3.4, “Setting Up Replication Using GTIDs”). This section explains transaction-based replication using global transaction identifiers (GTIDs). Because ...
https://dev.mysql.com/doc/refman/8.0/en/replication-mode-change-online-verify-transactions.html
The procedure is then: Do step 1 on A and step 2 on B. This section explains how to monitor a replication topology and verify that all anonymous transactions have been replicated. This is helpful when changing the replication mode online as you can ...
https://dev.mysql.com/doc/refman/8.0/en/replication-options-binary-log.html
For details of how stored programs (stored procedures and functions, triggers, and events) are handled when each binary logging format is set, see Section 27.7, “Stored Program Binary Logging”. Startup Options Used with Binary Logging System ...