PDF (US Ltr)
- 43.2Mb
PDF (A4)
- 43.3Mb
Man Pages (TGZ)
- 295.2Kb
Man Pages (Zip)
- 400.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/replication-features-partitioning.html
Replication is supported between partitioned tables as long as they use the same partitioning scheme and otherwise have the same structure, except where an exception is specifically allowed (see Section 19.5.1.9, “Replication with Differing Table ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-reserved-words.html
You can encounter problems when you attempt to replicate from an older source to a newer replica and you make use of identifiers on the source that are reserved words in the newer MySQL version running on the replica. For example, a table column ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-lifecycle.html
A GTID is also assigned to the creation, alteration, or deletion of a database, and of a non-table database object such as a procedure, function, trigger, event, view, user, role, or grant. The life cycle of a GTID consists of the following steps: ...
https://dev.mysql.com/doc/refman/8.0/en/replication-howto-additionalslaves.html
Alternatively, you can use the ALTER EVENT statement to set individual events to DISABLE or DISABLE ON SLAVE to prevent them from running on the new replica. As an alternative to creating a new replica in this way, MySQL Server's clone plugin can be ... You can add another replica to an existing replication configuration without stopping the source ...
https://dev.mysql.com/doc/refman/8.0/en/replication-options-source.html
If their values have already been modified from the default, Group Replication does not alter them. This section describes the server options and system variables that you can use on replication source servers. You can specify the options either on ...
https://dev.mysql.com/doc/refman/8.0/en/replication-rbr-safe-unsafe.html
The “safeness” of a statement in MySQL replication refers to whether the statement and its effects can be replicated correctly using statement-based format. If this is true of the statement, we refer to the statement as safe; otherwise, we ...
https://dev.mysql.com/doc/refman/8.0/en/replication-rules.html
For statements affecting databases only (that is, CREATE DATABASE, DROP DATABASE, and ALTER DATABASE), database-level options always take precedence over any --replicate-wild-do-table options. If a replication source server does not write a ...
https://dev.mysql.com/doc/refman/8.0/en/replication-setup-replicas.html
Alternatively, you can use the ALTER EVENT statement to set individual events to DISABLE or DISABLE ON SLAVE to prevent them from running on the new replica. As an alternative to creating a new replica in this way, MySQL Server's clone plugin can be ...Before you proceed, ensure that you have: Configured the source with the necessary configuration ...
https://dev.mysql.com/doc/refman/8.0/en/replication-upgrade.html
Alternatively, if you cannot stop new statements, temporarily change to row-based logging on the source (binlog_format=ROW) and wait until all replicas have processed all binary logs produced up to the point of this change, then upgrade the replicas. Perform any table repair or rebuilding operations needed to re-create database objects, such as use of REPAIR TABLE or ALTER TABLE, or dumping and reloading tables or ... When you ...
https://dev.mysql.com/doc/refman/8.0/en/security-guidelines.html
In discussing security, it is necessary to consider fully protecting the entire server host (not just the MySQL server) against all types of applicable attacks: eavesdropping, altering, playback, and denial of service. Anyone using MySQL on a ...