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/point-in-time-recovery-positions.html
The last section, Section 7.5.1, “Point-in-Time Recovery Using Binary Log”, explains the general idea of using the binary log to perform a point-in-time-recovery. As an example, suppose that around 13:00:00 on May 27, 2020, an SQL statement was ...
https://dev.mysql.com/doc/refman/5.7/en/privileges-provided.html
The PROCESS privilege also enables use of the SHOW ENGINE statement, access to the INFORMATION_SCHEMA InnoDB tables (tables with names that begin with INNODB_), and (as of MySQL 5.7.31) access to the INFORMATION_SCHEMA FILES table. The privileges ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-auto-increment.html
(Bug #11754117, Bug #45670) This issue does not affect tables using the InnoDB storage engine, since an InnoDB table with an AUTO_INCREMENT column requires at least one key where the auto-increment column is the only or leftmost column.
https://dev.mysql.com/doc/refman/5.7/en/replication-features-shutdowns.html
For the greatest possible durability and consistency in a replication setup using InnoDB with transactions, you should also set innodb_flush_log_at_trx_commit=1. With this setting, the contents of the InnoDB redo log buffer are written out to the ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-timeout.html
The total retry count can be seen in the output of SHOW STATUS; see Section 5.1.9, “Server Status Variables”.
https://dev.mysql.com/doc/refman/5.7/en/replication-features-transactions.html
For example, you can replicate an InnoDB source table as a MyISAM replica table. It is also safe to replicate transactions from MyISAM tables on the source to transactional tables, such as tables that use the InnoDB storage engine, on the replica.
https://dev.mysql.com/doc/refman/5.7/en/replication-features-truncate.html
However this caused issues when logging or replicating, in STATEMENT or MIXED mode, tables that used transactional storage engines such as InnoDB when the transaction isolation level was READ COMMITTED or READ UNCOMMITTED, which precludes ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features.html
For additional information specific to replication and InnoDB, see Section 14.20, “InnoDB and MySQL Replication”. The following sections provide information about what is supported and what is not in MySQL replication, and about specific issues ...
https://dev.mysql.com/doc/refman/5.7/en/replication-howto-additionalslaves.html
For example, the InnoDB system tablespace, undo tablespace, and redo log might be stored in an alternative location. InnoDB tablespace files and file-per-table tablespaces might have been created in other directories. You can add another replica to ...
https://dev.mysql.com/doc/refman/5.7/en/replication-howto.html
If you are using InnoDB, you do not need a read-lock and a transaction that is long enough to transfer the data snapshot is sufficient. This section describes how to set up a MySQL server to use binary log file position based replication. There are ...