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-features-partitioning.html
When the replica's copy of the table is partitioned but the source's copy is not, statements that act directly on partitions cannot be run on the source without causing errors there. Replication is supported between partitioned tables as long as ...
https://dev.mysql.com/doc/refman/8.0/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/8.0/en/replication-features-views.html
Trying to do so when row-based logging is in effect causes an error. Views are filtered by their own name, not by the tables they refer to. This means that a view can be replicated to the replica even if the view contains a table that would normally ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-assign-anon.html
If the replica server is started without GTIDs enabled and with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS set for any replication channels, the settings are not changed, but a warning message is written to the error log explaining how to change the ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-failover.html
When restoring a replica in a GTID based replication setup that has encountered an error, injecting an empty transaction may not solve the problem because an event does not have a GTID. There are a number of techniques when using MySQL Replication ...
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. This section provides examples of stored functions (see Chapter 27, Stored Objects) which you can create using some of the built-in functions ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-lifecycle.html
If the GTID has already been used, no error is raised, and the auto-skip function is used to ignore the transaction. The life cycle of a GTID consists of the following steps: A transaction is executed and committed on the source. This client ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-restrictions.html
This causes statements of any of the types discussed previously in this section to fail with an error. Because GTID-based replication is dependent on transactions, some features otherwise available in MySQL are not supported when using it. This ...
https://dev.mysql.com/doc/refman/8.0/en/replication-mode-change-online-enable-gtids.html
You must ensure that no warnings are being generated in the error logs before going to the next step. This section describes how to enable GTID transactions, and optionally auto-positioning, on servers that are already online and using anonymous ...
https://dev.mysql.com/doc/refman/8.0/en/replication-options-gtids.html
DROP TABLE or DROP TEMPORARY TABLE fails with an explicit error when used on a combination of nontemporary tables with temporary tables, or of temporary tables using transactional storage engines with temporary tables using nontransactional storage ... The MySQL Server system variables described in this section are used to monitor and control Global Transaction Identifiers ...