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/proxy-users.html
By proxied_user for itself: The value of USER() must exactly match CURRENT_USER() and proxied_user, for both the user name and host name parts of the account name. Both accounts have the same user part (''), which matches any user. The plugin that ...
https://dev.mysql.com/doc/refman/8.0/en/replication-encrypted-connections.html
To use an encrypted connection for the transfer of the binary log required during replication, both the source and the replica servers must support encrypted network connections. The connection procedure negotiates the use of the highest TLS ...If ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-errors.html
If a statement produces the same error (identical error code) on both the source and the replica, the error is logged, but replication continues. This includes the case that a statement produces an error on the source or the replica, but not both.
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-auto-positioning.html
Disabling the SOURCE_AUTO_POSITION | MASTER_AUTO_POSITION option again causes the replica to revert to position-based replication; this means that, when GTID_ONLY=ON, some positions may be marked as invalid, in which case you must also specify both ... GTIDs replace the file-offset pairs previously required to determine points for starting, stopping, or resuming the flow of data between source and ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-failover.html
The easiest way to reproduce all identifiers and transactions on a new server is to make the new server into the replica of a source that has the entire execution history, and enable global transaction identifiers on both servers. Alternatively, ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-functions.html
Having identical GTIDs present on both servers causes errors when copying database db2 to server1. In this scenario, source1 and source2 are both sources and replicas and replicate to each other. This section provides examples of stored functions ...
https://dev.mysql.com/doc/refman/8.0/en/replication-privilege-checks.html
By default, MySQL replication (including Group Replication) does not carry out privilege checks when transactions that were already accepted by another server are applied on a replica or group member. MySQL then checks each transaction against the ...
https://dev.mysql.com/doc/refman/8.0/en/replication-problems.html
Verify that the server_id system variable was set at startup on both the source and replica and that the ID value is unique on each server. Use SHOW REPLICA STATUS to check whether the Replica_IO_Running and Replica_SQL_Running values are both Yes.
https://dev.mysql.com/doc/refman/8.0/en/replication-sbr-rbr.html
(Row-based replication, however, simply replicates the value returned by the function or stored program, so its effect on table rows and data is the same on both the source and replica.) See Section 19.5.1.16, “Replication of Invoked Features”, ...For most users, the mixed replication format should provide the best combination of data integrity and ...
https://dev.mysql.com/doc/refman/8.0/en/replication-semisync-installation.html
You cannot have both the new and the old versions of the relevant plugin installed on an instance. The plugins must be enabled both on the source side and the replica side to enable semisynchronous replication. Semisynchronous replication is ...