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-json.html
The logging behavior depends on the format used, as described here: Statement-based replication. Before MySQL 8.0, an update to a JSON column was always written to the binary log as the complete document. In MySQL 8.0, it is possible to log partial ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-mysqldb.html
Data modification statements made to tables in the mysql schema are replicated according to the value of binlog_format; if this value is MIXED, these statements are replicated using row-based format. However, statements that would normally update ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-row-searches.html
When a replica using row-based replication format applies an UPDATE or DELETE operation, it must search the relevant table for the matching rows. The algorithm used to carry out this process uses one of the table's indexes to carry out the search ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-transaction-inconsistencies.html
The source binary log position information is persisted in binary format in the internal table mysql.slave_worker_info. START REPLICA [SQL_THREAD] always consults this information so that it applies only the correct transactions. Thus issuing RESET ... 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-features-truncate.html
TRUNCATE TABLE is normally regarded as a DML statement, and so would be expected to be logged and replicated using row-based format when the binary logging mode is ROW or MIXED. However this caused issues when logging or replicating, in STATEMENT ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-functions.html
See Section 14.18.2, “Functions Used with Global Transaction Identifiers (GTIDs)”, more more information about the functions just listed. This section provides examples of stored functions (see Chapter 27, Stored Objects) which you can create ...
https://dev.mysql.com/doc/refman/8.0/en/replication-multi-source-provision-replica.html
This statement transfers the GTIDs for the transactions executed on the source to the replica, and the replica requires this information. If the sources in the multi-source replication topology have existing data, it can save time to provision the ...
https://dev.mysql.com/doc/refman/8.0/en/replication-privilege-checks.html
When REQUIRE_ROW_FORMAT is set, you must use row-based binary logging (binlog_format=ROW) on the source server. In MySQL 8.0.18, REQUIRE_ROW_FORMAT is not available, but the use of row-based binary logging for secured replication channels is still ... By default, MySQL replication (including Group Replication) does not carry out privilege checks when transactions that were already accepted by another server are applied on a replica or group ...
https://dev.mysql.com/doc/refman/8.0/en/replication-rules-channel-based-filters.html
For instructions to set up replication channels, see Section 19.1.5, “MySQL Multi-Source Replication”, and for more information on how they work, see Section 19.2.2, “Replication Channels”. The following command options support channel ...
https://dev.mysql.com/doc/refman/8.0/en/roles.html
To create the roles, use the CREATE ROLE statement: CREATE ROLE 'app_developer', 'app_read', 'app_write'; Role names are much like user account names and consist of a user part and host part in 'user_name'@'host_name' format. Like user accounts, ...