MySQL Bugs: #34141: mysqlbinlog cannot read 4.1 binlogs containing load data infile

Bug #34141	mysqlbinlog cannot read 4.1 binlogs containing load data infile
Submitted:	29 Jan 2008 17:36	Modified:	16 Feb 2008 11:16
Reporter:	Sven Sandberg	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S3 (Non-critical)
Version:	5.1	OS:	Any
Assigned to:	Sven Sandberg	CPU Architecture:	Any
Tags:	create_file_log_event, LOAD DATA INFILE, mysqlbinlog

View
Add Comment
Files
Developer
Edit Submission
View Progress Log
Contributions

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

first binlog

Attachment: binlog-4.1-load-minimal.000001 (application/octet-stream, text), 227 bytes.

second binlog

Attachment: binlog-4.1-load-small.000001 (application/octet-stream, text), 251 bytes.