PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 296.5Kb
Man Pages (Zip)
- 401.9Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/replication-binlog-encryption-scope.html
Existing binary log files and relay log files that were present on the server when you started encryption are not encrypted. You can purge these files when they are no longer needed. Data in motion in the replication event stream, which is sent to ...
https://dev.mysql.com/doc/refman/8.0/en/replication-binlog-encryption.html
If you activate encryption while the server is running, a new binary log encryption key is generated at that time. From MySQL 8.0.14, binary log files and relay log files can be encrypted, helping to protect these files and the potentially ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-differing-tables.html
A column's default value is determined by a number of factors, including its type, whether it is defined with a DEFAULT option, whether it is declared as NULL, and the server SQL mode in effect at the time of its creation; for more information, see ... Source and target tables for replication do not have to be ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-memory.html
To replicate this effect to replicas, the first time that the source uses a given MEMORY table after startup, it logs an event that notifies replicas that the table must be emptied by writing a DELETE or (from MySQL 8.0.22) TRUNCATE TABLE statement ... When a replication source server shuts down and restarts, its MEMORY tables become ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-transaction-inconsistencies.html
When using a multithreaded replica, workers which have not received an error complete their queues, so it may take time to stop all threads. After this timeout, the coordinator gives up and aborts the transaction. After this timeout, it aborts the ... Inconsistencies in the sequence of transactions that have been executed from the relay log can occur depending on your replication ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-functions.html
If some of the replicas are experiencing replication lag, this stored function can be used to compute the most up-to-date replica without waiting for all the replicas to apply their existing relay logs, and therefore to minimize the failover time.
https://dev.mysql.com/doc/refman/8.0/en/replication-mode-change-online-concepts.html
gtid_mode can be changed only one step at a time, based on the order of the values as shown in the previous list. Before setting the replication mode of an online server, it is important to understand some key concepts of replication. This section ...
https://dev.mysql.com/doc/refman/8.0/en/replication-mode-change-online-disable-gtids.html
If you use binary logs for anything other than replication—for example, to perform point-in-time backup or restore—wait until you no longer need any old binary logs containing GTID transactions. This section describes how to disable GTID ...
https://dev.mysql.com/doc/refman/8.0/en/replication-problems.html
Many users have lost time by not doing this soon enough after encountering problems. If you have followed the instructions but your replication setup is not working, the first thing to do is check the error log for messages. If you cannot tell from ...
https://dev.mysql.com/doc/refman/8.0/en/replication-rbr-usage.html
You can switch from statement-based to row-based binary logging format at runtime even when temporary tables have been created. However, in MySQL 8.0, you cannot switch from row-based or mixed format for binary logging to statement-based format at ... MySQL uses statement-based logging (SBL), row-based logging (RBL) or mixed-format ...