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 | d44d6976d07570033640d3ef87cca05b20aaf24b (patch) | |
| tree | e439202deb9c5709108ea9af38614de7ef51c91d /libmysql_r | |
| parent | eadfe4ddfa810972daa323131f6cc1476eee8055 (diff) | |
| download | mariadb-git-d44d6976d07570033640d3ef87cca05b20aaf24b.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 'libmysql_r')
0 files changed, 0 insertions, 0 deletions