PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 256.4Kb
Man Pages (Zip)
- 361.2Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-setup-instruments-table.html
This affects primarily mutexes, conditions, and rwlocks in the server, although there may be other instruments for which this is true. (Events do not really have a “name,” but this provides a way to associate events with instruments.) ENABLED ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-thread-filtering.html
This includes wait, stage, statement, and transaction events and affects logging to these tables: events_waits_history events_waits_history_long events_stages_history events_stages_history_long events_statements_history ... The threads table ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-timing.html
This section discusses the available timers and their characteristics, and how timing values are represented in events. For this reason, the conversion is a quick and fairly rough multiplication operation. This in turn causes those values to be ...
https://dev.mysql.com/doc/refman/5.7/en/replace.html
SELECT statements depend on the ordering of rows from the SELECT and this order cannot always be guaranteed, it is possible when logging these statements for the source and the replica to diverge. You should be aware that, if you do this, the ...
https://dev.mysql.com/doc/refman/5.7/en/replica-sql-thread-states.html
This state can only be encountered if the original LOAD DATA statement was logged by a source running a version of MySQL lower than MySQL 5.0.3. Waiting for Slave Workers to free pending events This waiting action occurs when the total size of ...
https://dev.mysql.com/doc/refman/5.7/en/replication-channels.html
This section describes how channels can be used in a replication topology, and the impact they have on single-source replication. This is because the server IDs of replicas must be unique in a replication topology. When you do this on a multi-source ... In MySQL multi-source replication, a replica opens multiple replication channels, one for each replication source ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-shutdowns.html
This can cause the replica not to be able to replicate when the source comes back up. Setting sync_binlog=1 in the source's my.cnf file helps to minimize this problem because it causes the source to flush its binary log more frequently. With this ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-triggers.html
It is sufficient to switch to statement-based replication only for those statements where you want this effect, and to use row-based replication the rest of the time. To avoid this problem, upgrade the replicas first, then upgrade the source. The ...
https://dev.mysql.com/doc/refman/5.7/en/replication-howto.html
This section describes how to set up a MySQL server to use binary log file position based replication. You need this information when configuring the replica so that the replica knows where in the binary log to start executing events. If you do not ...There are a number of different methods for setting up replication, and the exact method to use depends on how you are setting up replication, and whether you already have data in the database on the ...
https://dev.mysql.com/doc/refman/5.7/en/replication-semisync.html
This section discusses what semisynchronous replication is and how it works. Failover from source to replica in this case might result in failover to a server that is missing transactions relative to the source. If your goal is to implement a ... In ...