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-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 ...
https://dev.mysql.com/doc/refman/8.0/en/replication-options-source.html
Attempting to set the value of auto_increment_increment or auto_increment_offset to a noninteger value produces an error, and the actual value of the variable remains unchanged. This section describes the server options and system variables that ...
https://dev.mysql.com/doc/refman/8.0/en/replication-options.html
When starting, the replication I/O (receiver) thread generates an error and aborts if its source's UUID is equal to its own unless the --replicate-same-server-id option has been set. The following sections contain information about mysqld options ...
https://dev.mysql.com/doc/refman/8.0/en/selecting-all.html
For example, you may happen to think that the birth date for Bowser doesn't seem quite right. Consulting your original pedigree papers, you find that the correct birth year should be 1989, not 1979. Fix only the erroneous record with an UPDATE ...
https://dev.mysql.com/doc/refman/8.0/en/set-character-set.html
Attempting to use them with SET CHARACTER SET produces an error. SET {CHARACTER SET | CHARSET} {'charset_name' | DEFAULT} This statement maps all strings sent between the server and the current client with the given mapping. SET CHARACTER SET sets ...