Bug #17857 Binary logging of events does not work
Submitted: 2 Mar 2006 11:58 Modified: 6 May 2007 3:06
Reporter: Giuseppe Maxia Email Updates:
Status: Closed Impact on me:
Category:MySQL Server Severity:S1 (Critical)
Version:5.1.7 OS:Linux (Linux)
Assigned to: Chuck Bell CPU Architecture:Any

[2 Mar 2006 11:58] Giuseppe Maxia
Actions performed from scheduled events do not get written to the binary log.
Already reported in bug #16421, but only with reference to replication.
However, this lack of binary log recording will also affect the usability of the binary log for failover purposes.
Thus, I am reporting this problem as "serious".

How to repeat:
Set up an event in a replicationg system and check the results in both the master and the slave.
Changes made by the event are not recorded in the binary log, and in the slave.

Suggested fix:
Add support for binary logging for events.
[2 Mar 2006 14:47] Valeriy Kravchuk
Thank you for a problem report. I am marking it as a duplicate of bug #16421 and will try to get more attention to that bug from developers.
[29 Mar 2007 15:26] Chuck Bell
Patch for this bug included in WL#3629. Patch pushed 29 Mar 2007.
[31 Mar 2007 23:55] Bugs System
Pushed into 5.1.18-beta
[6 May 2007 3:06] Jon Stephens
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 bug fix. More information about accessing the source trees is available at


Documented fix in 5.1.18 changelog. Documented associated feature changes in Events, INFORMATION_SCHEMA, and Replication chapters of 5.1 Manual.