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
-
-
- Closed
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Link |
This issue blocks |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| issue.field.resolutiondate | 2018-08-01 12:19:02.0 | 2018-08-01 12:19:02.118 |
| Fix Version/s | 10.0.37 [ 22917 ] | |
| Fix Version/s | 10.1.36 [ 23117 ] | |
| Fix Version/s | 10.2.17 [ 23111 ] | |
| Fix Version/s | 10.3.9 [ 23114 ] | |
| Fix Version/s | 10.2 [ 14601 ] | |
| Fix Version/s | 10.0 [ 16000 ] | |
| Fix Version/s | 10.1 [ 16100 ] | |
| Fix Version/s | 10.3 [ 22126 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Closed [ 6 ] |
| Workflow | MariaDB v3 [ 88666 ] | MariaDB v4 [ 154735 ] |
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).