diff options
author | Monty <monty@mariadb.org> | 2018-05-26 16:57:18 +0300 |
---|---|---|
committer | Monty <monty@mariadb.org> | 2018-05-27 19:47:17 +0300 |
commit | 58721c3e38f1d5cd9261c6da205126cf0ae2ab24 (patch) | |
tree | 53d3a77617ca85823b5cae33eb257749990df2cc /sql/group_by_handler.cc | |
parent | b3a27618073c74ec5dbf0eeb57afeecf7e8bfa1c (diff) | |
download | mariadb-git-58721c3e38f1d5cd9261c6da205126cf0ae2ab24.tar.gz |
MDEV-16286 Killed CREATE SEQUENCE leaves sequence in unusable state
Fixed by deleting the sequence if we where not able to initialize it
I also noticed that we didn't always set the error message when
check_killed(), which could lead to aborted queries without error
beeing properly set. Fixed by default setting error message if
check_error() noticed that killed had been called.
This allowed me to remove a lot of calls to thd->send_kill_message().
Diffstat (limited to 'sql/group_by_handler.cc')
-rw-r--r-- | sql/group_by_handler.cc | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/sql/group_by_handler.cc b/sql/group_by_handler.cc index c92df8922ce..f18758a2d94 100644 --- a/sql/group_by_handler.cc +++ b/sql/group_by_handler.cc @@ -65,7 +65,6 @@ int Pushdown_query::execute(JOIN *join) { if (unlikely(thd->check_killed())) { - thd->send_kill_message(); handler->end_scan(); DBUG_RETURN(-1); } |