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/purge-binary-logs.html
This statement has no effect if the server was not started with the --log-bin option to enable binary logging. If you have an active replica that currently is reading one of the log files you are trying to delete, this statement does not delete the ... PURGE { BINARY | MASTER } LOGS { TO 'log_name' | BEFORE datetime_expr } The binary log is a set of files that contain information about data modifications made by the MySQL ...
https://dev.mysql.com/doc/refman/8.0/en/rename-table.html
For example, this is permitted: LOCK TABLE old_table1 WRITE; RENAME TABLE old_table1 TO new_table1, new_table1 TO new_table2; This is not permitted: LOCK TABLE old_table1 READ; RENAME TABLE old_table1 TO new_table1, new_table1 TO new_table2; Prior ... RENAME TABLE tbl_name TO new_tbl_name [, tbl_name2 TO new_tbl_name2] ...
https://dev.mysql.com/doc/refman/8.0/en/replication-asynchronous-connection-failover-replica.html
This is the case whether the sources are a managed group for which the membership is updated automatically, or whether they are added or changed manually using asynchronous_connection_failover_add_source(), ...To configure this feature, the ... In ...
https://dev.mysql.com/doc/refman/8.0/en/replication-asynchronous-connection-failover.html
However, you can delete a managed group manually if it is no longer needed. This feature works with Group Replication, on a group configured in single-primary mode, where the group’s primary is a replica that has a replication channel using the ...
https://dev.mysql.com/doc/refman/8.0/en/replication-bugs.html
In this case, the replication thread stops and waits for you to clean up the tables manually to bring them into synchrony. When you have determined that there is no user error involved, and replication still either does not work at all or is ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-flush.html
This is not normally a problem because these statements do not modify table data. In addition, if you use FLUSH TABLES when renaming a MyISAM table that is part of a MERGE table, you must issue FLUSH TABLES manually on the replicas. Some forms of ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-invoked.html
For example, trying to replicate a loadable function with statement-based replication generates this warning because it currently cannot be determined by the MySQL server whether the function is deterministic. In the case of CREATE EVENT and ALTER ... Replication of invoked features such as loadable functions and stored programs (stored procedures and functions, triggers, and events) provides the following characteristics: The effects of the feature are always ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-repair-table.html
However, any such modifications of table data performed by this statement are not replicated, which can cause source and replica to lose synchronization. When used on a corrupted or otherwise damaged table, it is possible for the REPAIR TABLE ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features.html
If you are planning to use statement-based replication between MySQL 8.0 and a previous MySQL release series, it is a good idea to consult the edition of the MySQL Reference Manual corresponding to the earlier release series for information ... The ...
https://dev.mysql.com/doc/refman/8.0/en/replication-howto-masterstatus.html
Warning This procedure uses FLUSH TABLES WITH READ LOCK, which blocks COMMIT operations for InnoDB tables. If you are planning to shut down the source to create a data snapshot, you can optionally skip this procedure and instead store a copy of the ... To configure the replica to start the replication process at the correct point, you need to note the source's current coordinates within its binary ...