mariadb/fts_kill_query.result at 94e9dc95d4bebf711f001e16bbb53fd8d6a58b8c - mariadb - GitFox

database/mariadb

mirror of https://github.com/MariaDB/server.git synced 2025-08-31 22:22:30 +03:00

Files

Marko Mäkelä a7f84f09bf MDEV-16865 InnoDB fts_query() ignores KILL

The functions fts_ast_visit() and fts_query() inside
InnoDB FULLTEXT INDEX query processing are not checking
for THD::killed (trx_is_interrupted()), like anything
that potentially takes a long time should do.

This is a port of the following change from MySQL 5.7.23,
with a completely rewritten test case.

commit c58c6f8f66ddd0357ecd0c99646aa6bf1dae49c8
Author: Aakanksha Verma <aakanksha.verma@oracle.com>
Date:   Fri May 4 15:53:13 2018 +0530

Bug #27155294 MAX_EXECUTION_TIME NOT INTERUPTED WITH FULLTEXT SEARCH USING MECAB

2018-08-01 08:43:12 +03:00

7 lines

196 B

Plaintext

Raw Blame History

 CREATE TABLE t1 (a VARCHAR(7), b text, FULLTEXT KEY idx (a,b)) ENGINE=InnoDB;
 COMMIT;
 SELECT COUNT(*) FROM t1
 WHERE MATCH (a,b) AGAINST ('foo bar' IN BOOLEAN MODE);
 KILL QUERY @id;
 DROP TABLE t1;