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.html
This enables you to determine how many times instrumented activities were performed and how much time they took. This is because collection is ongoing whereas retrieval is on demand and might never happen at all. This benefits developers of ... The ...
https://dev.mysql.com/doc/refman/5.7/en/point-in-time-recovery-binlog.html
This section explains the general idea of using the binary log to perform a point-in-time-recovery. Note Many of the examples in this and the next section use the mysql client to process binary log output produced by mysqlbinlog. This enables ...
https://dev.mysql.com/doc/refman/5.7/en/program-options.html
This is common for options that apply to a specific invocation of the program. This is common for options that you want the program to use each time it runs. This method is useful for options that you want to apply each time the program runs. In ...
https://dev.mysql.com/doc/refman/5.7/en/replica-io-thread-states.html
This state also appears in the Slave_IO_State column displayed by SHOW SLAVE STATUS, so you can get a good view of what is happening by using that statement. This can last for a long time if the source is idle. Waiting for the slave SQL thread to ...
https://dev.mysql.com/doc/refman/5.7/en/replica-logs-relaylog.html
On a Unix system, this can be done as shown here: $> cat new_relay_log_name.index >> old_relay_log_name.index $> mv old_relay_log_name.index new_relay_log_name.index A replica server creates a new relay log file under the following conditions: Each ... The relay log, like the binary log, consists of a set of numbered files containing events that describe database changes, and an index file that contains the names of all used relay log ...
https://dev.mysql.com/doc/refman/5.7/en/replication-compatibility.html
This restriction applies not only to release series, but to version numbers within the same release series as well. This is due to a number of factors: Binary log format changes. While we attempt to maintain backward compatibility, this is not ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-create-select.html
Some older versions of MySQL permitted these statements to do so; this means that, when using replication between a MySQL 5.6 or later replica and a source running a previous version of MySQL, a CREATE TABLE ... To prevent this from happening, you ...SELECT statement to make any changes in tables other than the table that is created by the ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-max-allowed-packet.html
If max_allowed_packet is too small on the replica, this also causes the replica to stop the replication I/O thread. This means that, when you are replicating large column values using row-based replication, you must take care to set ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-temptables.html
The discussion in the following paragraphs does not apply when binlog_format=ROW because, in that case, temporary tables are not replicated; this means that there are never any temporary tables on the replica to be lost in the event of an unplanned ...Loss of replicated temporary tables on the replica can be an issue, whenever binlog_format is STATEMENT or MIXED, for statements involving temporary tables that can be logged safely using statement-based ...
https://dev.mysql.com/doc/refman/5.7/en/replication-formats.html
This is called statement-based replication (which can be abbreviated as SBR), which corresponds to the MySQL statement-based binary logging format. This is called row-based replication (which can be abbreviated as RBR). Replication works because ...