binlog_format
WARNING
Rule IDs: bl_002
Overview
- Purpose
- Documented in the MySQL 8.4 manual as a server system variable (scope: Both). Purpose and semantics are described at the linked manual page.
- Dynamic (MySQL 8.4 reference)
- MySQL 8.4 marks this variable as dynamic (
Dynamic= Yes). Runtime changes useSET GLOBAL(global scope) orSET SESSION(session scope) — confirm syntax and persistence (SET PERSIST) in the manual. - Default value
- ROW (removed in 8.4; always ROW) (MySQL 8.4)
- Version and product notes
- MariaDB and Percona Server may use different names, defaults, or dynamic behavior; verify their documentation.
- Documentation
- https://dev.mysql.com/doc/refman/8.4/en/replication-options-binary-log.html#sysvar_binlog_format
- Other vendors
What is checked
Rules that reference this variable, with their severity and what each rule detects:
- WARNING
bl_002: Use binlog_format=ROW for safe, deterministic replication. In MySQL 8.4, ROW is the only option.
Tuning guidance
- Recommended actions:
- Use binlog_format=ROW for safe, deterministic replication. In MySQL 8.4, ROW is the only option.
- Trade-offs: Binary logging is essential for replication and point-in-time recovery. sync_binlog=1 guarantees durability but adds fsync overhead. ROW format is safest for replication consistency but produces larger binlogs.
Example
Consult the manual for whether SET GLOBAL, SET PERSIST, or SET SESSION applies.