Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.0(EOL), 10.1(EOL), 10.2(EOL), 10.3(EOL)
Description
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.
We should backport Bug #27155294 MAX_EXECUTION_TIME NOT INTERUPTED WITH FULLTEXT SEARCH USING MECAB PROBLEM from MySQL 5.7.23 to address this.
Attachments
Issue Links
- blocks
-
MDEV-16850 Merge new release of InnoDB 5.7.23 to 10.2
-
- Closed
-
The fix from upstream contained an error, which slipped into the 10.0.37 release, but will be fixed in MariaDB Server 10.0.38. A wrong pointer was tested for NULL in a clean-up code path, potentially leading to a SIGSEGV if a FULLTEXT INDEX query is killed (or the client disconnects before completion).