diff options
| author | andrey@whirlpool.hristov.com <> | 2008-02-22 16:18:31 +0100 |
|---|---|---|
| committer | andrey@whirlpool.hristov.com <> | 2008-02-22 16:18:31 +0100 |
| commit | b4fb43d8037ea56e5b81cb2d0a750868e6099cb5 (patch) | |
| tree | 3b43ae5c19e58834f54aac1104692f0891d63f47 /sql/events.cc | |
| parent | 301ab0d8b72bea5a924cd996f0a0378b3175e9db (diff) | |
| download | mariadb-git-b4fb43d8037ea56e5b81cb2d0a750868e6099cb5.tar.gz | |
Fix for bug#22738 Events: After stop and start disabled events could reside in the queue
Disabled events weren't removed from the memory queue after the scheduler has been
re-enabled. After recalculation of next execution time of an event, it might get disabled.
Diffstat (limited to 'sql/events.cc')
| -rw-r--r-- | sql/events.cc | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/sql/events.cc b/sql/events.cc index 87385082a82..700663db7d1 100644 --- a/sql/events.cc +++ b/sql/events.cc @@ -1185,7 +1185,12 @@ Events::load_events_from_db(THD *thd) { /* If not created, a stale event - drop if immediately if - ON COMPLETION NOT PRESERVE + ON COMPLETION NOT PRESERVE. + XXX: This won't be replicated, thus the drop won't appear in + in the slave. When the slave is restarted it will drop events. + However, as the slave will be "out of sync", it might happen that + an event created on the master, after master restart, won't be + replicated to the slave correctly, as the create will fail there. */ int rc= table->file->ha_delete_row(table->record[0]); if (rc) |