Binary Log

Understand the binary log in MariaDB Server. This section explains its role in replication and point-in-time recovery, detailing its format, management, and use for data integrity.

The binary log (binlog) contains a record of all changes to the databases.

Overview of the Binary Log

Introduction to the purpose and structure of the binary log, explaining how it records data changes (DML) and structure changes (DDL) for replication and recovery.

Activating the Binary Log

Instructions for enabling the binary log using the --log-bin option and configuring the log file basename and index file.

Binary Log Formats

Detailed comparison of the three binary logging formats: Statement-based (SBR), Row-based (RBR), and Mixed, including their pros, cons, and configuration via binlog_format.

Using and Maintaining the Binary Log

Complete binary log maintenance: PURGE BINARY LOGS/RESET MASTER, expire_logs_days & binlog_expire_logs_seconds, FLUSH BINARY LOGS, and SHOW SLAVE STATUS.

InnoDB-Based Binary Log

MariaDB 12.3 introduces a new binary log implementation that stores binlog events directly in InnoDB-managed tablespaces instead of separate files on disk.

Compressing Events to Reduce Size of the Binary Log

Guide to using the log_bin_compress system variable to compress binary log events, reducing storage usage and network bandwidth during replication.

Flashback

Explains how to use the Flashback feature (via mysqlbinlog --flashback) to rollback transactions by reversing the binary log events, useful for recovering from accidental data modifications.

Group Commit for the Binary Log

Describes the group commit optimization, which improves performance by committing multiple transactions to the binary log in a single disk I/O operation.

Relay Log

Overview of the relay log, a set of log files created by a replica server to store events received from the primary's binary log before executing them.

Selectively Skipping Replication of Binlog Events

Learn techniques to bypass specific replication events. This guide explains how to ignore individual transactions or errors to restore replication flow after a stoppage.