diff options
| author | unknown <guilhem@mysql.com> | 2004-03-08 14:47:13 +0100 |
|---|---|---|
| committer | unknown <guilhem@mysql.com> | 2004-03-08 14:47:13 +0100 |
| commit | fd84865393dd45d89aa03d53d9c7a23303818975 (patch) | |
| tree | e439202deb9c5709108ea9af38614de7ef51c91d /innobase/buf | |
| parent | 8cbfb5fb0cea1e9a2ec7e4ea52f36065774a88d3 (diff) | |
| download | mariadb-git-fd84865393dd45d89aa03d53d9c7a23303818975.tar.gz | |
Fix for BUG#3081 "if an INSERT DELAYED is killed, it is binlogged as killed but it's not needed".
INSERT DELAYED works only for one-row inserts (in latest 4.0 versions
at least). So killing a delayed_insert thread does not spoil replication:
the rows which actually went into the table are exactly those listed
in the binlog. So when the delayed_insert thread is killed, don't log
it as 'killed', because it causes superfluous stops on the slave.
sql/log_event.cc:
INSERT DELAYED works only for one-row inserts (in latest 4.0 versions
at least). So killing a delayed_insert thread does not spoil replication:
the rows which actually went into the table are exactly those listed
in the binlog. So when the delayed_insert thread is killed, don't log
it as 'killed', because it causes superfluous stops on the slave.
Diffstat (limited to 'innobase/buf')
0 files changed, 0 insertions, 0 deletions