MySQL Bugs: #120430: Support InnoDB-based binary log (transactional binlog stored within InnoDB)

Bug #120430	Support InnoDB-based binary log (transactional binlog stored within InnoDB)
Submitted:	10 May 19:04
Reporter:	Vinicius Malvestio Grippa (OCA)	Email Updates:
Status:	Open	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S4 (Feature request)
Version:		OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	ROADMAP_CANDIDATE

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

Support InnoDB-based binary log Design Proposal

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

Presentation for the proposed feature.

Attachment: Oracle - Support InnoDB-based binary log (transactional binlog stored within InnoDB).pptx (application/vnd.openxmlformats-officedocument.presentationml.presentation, text), 5.51 MiB.