PDF (US Ltr)
- 41.9Mb
PDF (A4)
- 42.0Mb
Man Pages (TGZ)
- 272.3Kb
Man Pages (Zip)
- 378.3Kb
Info (Gzip)
- 4.2Mb
Info (Zip)
- 4.2Mb
Search Results
https://dev.mysql.com/doc/refman/9.7/en/replication-features-js-programs.html
A JavaScript stored program created on a server without the component installed is not checked for validity. This means that, when a CREATE FUNCTION or CREATE PROCEDURE statement without USING, and which contains invalid JavaScript code, is executed ...
https://dev.mysql.com/doc/refman/9.7/en/replication-features-sql-mode.html
Using different server SQL mode settings on the source and the replica may cause the same INSERT statements to be handled differently on the source and the replica, leading the source and replica to diverge. For best results, you should always use ...
https://dev.mysql.com/doc/refman/9.7/en/replication-features-transactions.html
In MySQL 26.10 (and later), transactions that update both transactional tables and tables which are nontransactional or noncomposable are deprecated, and causes a deprecation warning to be written to both the client and the error log. In MySQL 26.10 ...
https://dev.mysql.com/doc/refman/9.7/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/9.7/en/replication-gtids-auto-positioning.html
GTIDs replace the file-offset pairs previously required to determine points for starting, stopping, or resuming the flow of data between source and replica. When GTIDs are in use, all the information that the replica needs for synchronizing with ...
https://dev.mysql.com/doc/refman/9.7/en/replication-options-gtids.html
The MySQL Server system variables described in this section are used to monitor and control Global Transaction Identifiers (GTIDs). For additional information, see Section 19.1.3, “Replication with Global Transaction Identifiers”.
https://dev.mysql.com/doc/refman/9.7/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/9.7/en/replication-rules-channel-based-filters.html
This section explains how to work with replication filters when multiple replication channels exist, for example in a multi-source replication topology. Replication filters can be global or specific to a channel, enabling you to configure ...
https://dev.mysql.com/doc/refman/9.7/en/replication-rules-examples.html
If you use a combination of database-level and table-level replication filtering options, the replica first accepts or ignores events using the database options, then it evaluates all events permitted by those options according to the table options. It is also important to note that the results vary depending on whether the operation is logged using statement-based or row-based binary logging ...
https://dev.mysql.com/doc/refman/9.7/en/replication-solutions.html
Replication can be used in many different environments for a range of purposes. This section provides general notes and advice on using replication for specific solution types. For information on using replication in a backup environment, including ...