Search Results
https://dev.mysql.com/doc/refman/8.4/en/replace.html
such statements produce a warning in the error log when using statement-based mode and are written to the binary log using the row-based format when using MIXED mode. REPLACE [LOW_PRIORITY | DELAYED] [INTO] tbl_name [PARTITION (partition_name [, ...
https://dev.mysql.com/doc/refman/8.4/en/replication-binlog-encryption-encryption-keys.html
The file password is encrypted using AES-CBC (AES Cipher Block Chaining mode) with the 256-bit binary log encryption key and a random initialization vector (IV), and is stored in the log file's file header. The file data is encrypted using AES-CTR ... The binary log encryption keys used to encrypt the file passwords for the log files are 256-bit keys that are generated specifically for each MySQL server instance using MySQL Server's keyring service (see Section 8.4.4, “The MySQL ...
https://dev.mysql.com/doc/refman/8.4/en/replication-encrypted-connections.html
For a replication connection, specifying a value for either of SOURCE_SSL_CA or SOURCE_SSL_CAPATH corresponds to setting --ssl-mode=VERIFY_CA. To activate host name identity verification, add the SOURCE_SSL_VERIFY_SERVER_CERT option, like this: -> ... To use an encrypted connection for the transfer of the binary log required during replication, both the source and the replica servers must support encrypted network ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-directory.html
This can be overridden by using the NO_DIR_IN_CREATE server SQL mode on the replica, which causes the replica to ignore the DATA DIRECTORY and INDEX DIRECTORY table options when replicating CREATE TABLE statements. If a DATA DIRECTORY or INDEX ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-truncate.html
TRUNCATE TABLE is normally regarded as a DML statement, and so would be expected to be logged and replicated using row-based format when the binary logging mode is ROW or MIXED. However this caused issues when logging or replicating, in STATEMENT ...TRUNCATE TABLE is treated for purposes of logging and replication as DDL rather than DML so that it can be logged and replicated as a ...
https://dev.mysql.com/doc/refman/8.4/en/replication-gtids-failover.html
If you use this method, the replica must be configured for GTID-based replication, in other words with gtid_mode=ON. There are a number of techniques when using MySQL Replication with Global Transaction Identifiers (GTIDs) for provisioning a new ...
https://dev.mysql.com/doc/refman/8.4/en/set.html
Duplicate values in the definition cause a warning, or an error if strict SQL mode is enabled. A SET is a string object that can have zero or more values, each of which must be chosen from a list of permitted values specified when the table is ...
https://dev.mysql.com/doc/refman/8.4/en/show-triggers.html
row *************************** Trigger: ins_sum Event: INSERT Table: account Statement: SET @sum = @sum + NEW.amount Timing: BEFORE Created: 2018-08-08 10:10:12.61 sql_mode: ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES, NO_ZERO_IN_DATE,NO_ZERO_DATE, ...
https://dev.mysql.com/doc/refman/8.4/en/start-replica.html
In MySQL 8.4, this is no longer an issue, and SQL_AFTER_GTIDS can be used without causing the replica to fall back into single-threaded mode. If GTIDs are not in use and you need to change a failed multithreaded replica to single-threaded mode, you ... START REPLICA [thread_types] [until_option] [connection_options] [channel_option] thread_types: [thread_type [, thread_type] ...
https://dev.mysql.com/doc/refman/8.4/en/storage-engine-setting.html
For example, in a replication setup, perhaps your source server uses InnoDB tables for maximum safety, but the replica servers use other storage engines for speed at the expense of durability or concurrency. To prevent confusing, unintended behavior ... When you create a new table, you can specify which storage engine to use by adding an ENGINE table option to the CREATE TABLE statement: -- ENGINE=INNODB not needed unless you have set a different -- default storage ...