Because GTID-based replication is dependent on transactions, some features otherwise available in MySQL are not supported when using it. This section provides information about restrictions on and limitations of replication with GTIDs.
Updates involving nontransactional storage engines.
When using GTIDs, updates to tables using nontransactional
storage engines such as
cannot be made in the same statement or transaction as updates
to tables using transactional storage engines such as
This restriction is due to the fact that updates to tables that use a nontransactional storage engine mixed with updates to tables that use a transactional storage engine within the same transaction can result in multiple GTIDs being assigned to the same transaction.
Such problems can also occur when the master and the slave use different storage engines for their respective versions of the same table, where one storage engine is transactional and the other is not.
In any of the cases just mentioned, the one-to-one correspondence between transactions and GTIDs is broken, with the result that GTID-based replication cannot function correctly.
CREATE TABLE ... SELECT statements.
TABLE ... SELECT is not safe for statement-based
replication. When using row-based replication, this statement is
actually logged as two separate events—one for the
creation of the table, and another for the insertion of rows
from the source table into the new table just created. When this
statement is executed within a transaction, it is possible in
some cases for these two events to receive the same transaction
identifier, which means that the transaction containing the
inserts is skipped by the slave. Therefore,
TABLE ... SELECT is not supported when using
TABLE statements are not supported inside transactions
when using GTIDs (that is, when the server was started with the
option). It is possible to use these statements with GTIDs
enabled, but only outside of any transaction, and only with
Preventing execution of unsupported statements.
To prevent execution of statements that would cause GTID-based
replication to fail, all servers must be started with the
when enabling GTIDs. This causes statements of any of the types
discussed previously in this section to fail with an error.
For information about other required startup options when enabling GTIDs, see Section 188.8.131.52, “Setting Up Replication Using GTIDs”.
sql_slave_skip_counter is not
supported when using GTIDs. If you need to skip transactions, use
the value of the master's
gtid_executed variable instead;
see Injecting empty transactions, for more
GTID mode and mysqldump. It is possible to import a dump made using mysqldump into a MySQL Server running with GTID mode enabled, provided that there are no GTIDs in the target server's binary log.
GTID mode and mysql_upgrade.
It is possible but is not recommended to use
mysql_upgrade on a MySQL Server running with
mysql_upgrade can make changes to system
tables that use the
engine, which is nontransactional.