Bug #120430 Support InnoDB-based binary log (transactional binlog stored within InnoDB)

• Submitted: 10 May 19:04
• Reporter: Vinicius Malvestio Grippa
• Status: Open
• Category: MySQL Server: Replication
• Severity: S4 (Feature request)
• OS: Any
• CPU Architecture: Any
• Tags: ROADMAP_CANDIDATE

[10 May 19:04] Vinicius Malvestio Grippa

Description:
The binary log is currently a separate, file-based log written outside InnoDB's transactional layer. Every durable, replicated commit pays for two fsyncs (sync_binlog=1 + innodb_flush_log_at_trx_commit=1) and a two-phase commit between redo and binlog, plus a non-trivial crash-recovery reconciliation. Storing binlog events inside InnoDB would collapse this into a single durability domain.

Why it matters:

Performance: one fsync per commit on the hot path; simpler group commit.

Reliability: single recovery pass over InnoDB redo, no XA reconciliation between two logs.

Operability: binlog state is transactional — queryable, purgeable, and backed up atomically with the data.

Ecosystem: CDC consumers (Debezium, Maxwell, Readyset, ProxySQL mirroring) get a log that is transactionally consistent with the rows they read.

How to repeat:
N/A

Suggested fix:
N/A

[10 May 19:05] Vinicius Malvestio Grippa

Support InnoDB-based binary log Design Proposal

Attachment: mysql-community-design-proposal.json (application/json, text), 11.79 KiB.