Bug #1091 mysqlbinlog segfaults if --position is just before Exec_load event
Submitted: 19 Aug 2003 6:00 Modified: 19 Aug 2003 6:54
Reporter: Guilhem Bichot Email Updates:
Status: Closed Impact on me:
Category:MySQL Server Severity:S3 (Non-critical)
Version:4.0 OS:Any (all)
Assigned to: Guilhem Bichot CPU Architecture:Any

[19 Aug 2003 6:00] Guilhem Bichot
This is because when it reads an Exec_load, mysqlbinlog expects to have already read a Create_file.
But if used with --position to start the read between the 2 events, mysqlbinlog does not have the Create_file.
Other minor problem: if mysqlbinlog reads a Append_block without having read the Create_file, it stops. It should not, because it can be because of --position.

How to repeat:
Do a LOAD DATA INFILE, and do mysqlbinlog --position=X on the binlog, where X is the position of the Exec_load event.

Suggested fix:
Print warnings when there is no Create_file event before.
[19 Aug 2003 6:48] Guilhem Bichot
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at

ChangeSet@1.1553.14.1, 2003-08-19 15:12:44+02:00, guilhem@mysql.com