Search Results
https://dev.mysql.com/doc/refman/8.4/en/replication-binlog-encryption-encryption-keys.html
{SEQ_NO} is the sequence number for the binary log encryption key, which is incremented by 1 for each new key that is generated on the server. It automatically generates a new binary log encryption key using its own generated UUID, and uses this to ... 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-options-reference.html
max_relay_log_size: If nonzero, relay log is rotated automatically when its size exceeds this value. relay_log_recovery: Whether automatic recovery of relay log files from source at startup is enabled; must be enabled for crash-safe replica. The ...
https://dev.mysql.com/doc/refman/8.4/en/replication-privilege-checks-recover.html
For instructions to do this, see Section 9.5, “Point-in-Time (Incremental) Recovery”. To skip a transaction, if GTIDs are in use, commit an empty transaction that has the GTID of the failing transaction, for example: SET ... If a privilege check ...
https://dev.mysql.com/doc/refman/8.4/en/show-status.html
Each invocation of the SHOW STATUS statement uses an internal temporary table and increments the global Created_tmp_tables value. SHOW [GLOBAL | SESSION] STATUS [LIKE 'pattern' | WHERE expr] SHOW STATUS provides server status information (see ...
https://dev.mysql.com/doc/refman/8.4/en/update.html
If you update a column that has been declared NOT NULL by setting to NULL, an error occurs if strict SQL mode is enabled; otherwise, the column is set to the implicit default value for the column data type and the warning count is incremented.
https://dev.mysql.com/doc/refman/8.4/en/which-version.html
This is incremented for each new LTS release, but is likely always 0 for innovation releases. When preparing to install MySQL, decide which version and distribution format (binary or source) to use. First, decide whether to install from an LTS ...
https://dev.mysql.com/doc/relnotes/mysql/8.4/en/news-8-4-6.html
(Bug #36538081) InnoDB: A long semaphore wait crash could occur when a redo log consumer lagged behind after a failed MySQL Enterprise Backup incremental backup, preventing the redo log writer thread from advancing. (Bug #116239, Bug #37105430, Bug ... Note These release notes were created with the assistance of MySQL HeatWave ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/advanced.source.html
To fix a corruption problem in a replication source database, you can restore the backup, taking care not to propagate unnecessary SQL operations to the replica servers: Shut down the source database and then use, for example, the ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/backup-apply-log.html
For backups that are non-incremental, you can combine the initial backup and the apply-log steps using the backup-and-apply-log command. A directory backup, just like a single-file backup, can be prepared and restored using the ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/backup-commands.html
The major groups of commands are: Backup operations: backup, backup-and-apply-log, backup-to-image Update operations: apply-log, apply-incremental-backup Restore operations: copy-back, copy-back-and-apply-log Validation operation: validate ...Only ...