Bug #28293 mysqlbinlog: corrupt SQL in hex dump mode [PATCH INCLUDED]

Submitted: 8 May 2007 0:38 Modified: 3 Jul 2007 18:46
Reporter: Jon Anderson Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Command-line Clients Severity:S3 (Non-critical)
Version:5.0.44-BK, 5.0.37 OS:Any
Assigned to: Gleb Shchepa CPU Architecture:Any
Tags: Contribution

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
[8 May 2007 0:41] Jon Anderson 
Patch for sql/log_event.cc. A possible fixe for this bug.

Attachment: sql_log_event_cc.patch (application/octet-stream, text), 362 bytes.
[8 May 2007 14:05] Jon Anderson 
Binary log that triggers this bug in hexdump mode.

Attachment: binlog-error (application/octet-stream, text), 349 bytes.
[8 May 2007 14:05] Jon Anderson 
A binary log that does not trigger this bug.

Attachment: binlog-noerror (application/octet-stream, text), 348 bytes.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.040 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.