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	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

File:	Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

On *nix platforms use the split command e.g. split -b 50MB <my_large_archive> <my_split_archive_prefix>
On windows use WinZip or a similar utility to split the large file

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.