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/performance-schema-replication-group-member-actions-table.html
This table lists the member actions that are included in the member actions configuration for replication group members. You can reset the member actions configuration using the group_replication_reset_member_actions() function. The ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-statement-summary-tables.html
Each row summarizes events for a given stored program (stored procedure or function, trigger, or event). The Performance Schema maintains tables for collecting current and recent statement events, and aggregates that information in summary tables.
https://dev.mysql.com/doc/refman/8.0/en/prepare.html
For some combinations of actual type and derived type, an automatic repreparation of the statement is triggered, to ensure closer compatibility with previous versions of MySQL. PREPARE stmt_name FROM preparable_stmt The PREPARE statement prepares a ...
https://dev.mysql.com/doc/refman/8.0/en/replication-asynchronous-connection-failover.html
You can use administrator commands to trigger a controlled switchover or emergency failover between groups if the primary cluster is not functioning normally. Beginning with MySQL 8.0.22, you can use the asynchronous connection failover mechanism ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-auto-increment.html
Statement-based replication of AUTO_INCREMENT, LAST_INSERT_ID(), and TIMESTAMP values is carried out subject to the following exceptions: A statement invoking a trigger or function that causes an update to an AUTO_INCREMENT column is not replicated ...(Bug #45677) An INSERT into a table that has a composite primary key that includes an AUTO_INCREMENT column that is not the first column of this composite key is not safe for statement-based logging or ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-current-user.html
In some cases, such as statements that change passwords, the function reference is expanded before it is written to the binary log, so that the statement includes the user name. For all other cases, the name of the current user on the source is ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-drop-if-exists.html
IF EXISTS statements for stored programs (stored procedures and functions, triggers, and events) are also replicated, even if the stored program to be dropped does not exist on the source. The DROP DATABASE IF EXISTS, DROP TABLE IF EXISTS, and DROP ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-mysqldb.html
However, statements that would normally update this information indirectly—such GRANT, REVOKE, and statements manipulating triggers, stored routines, and views—are replicated to replicas using statement-based replication. Data modification ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-temptables.html
In statement-based replication mode, CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE statements cannot be used inside a transaction, procedure, function, or trigger when GTIDs are in use on the server (that is, when the enforce_gtid_consistency ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features.html
With MySQL's statement-based replication, there may be issues with replicating stored routines or triggers. The following sections provide information about what is supported and what is not in MySQL replication, and about specific issues and ...