Details

    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

          Activity

            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).

            marko Marko Mäkelä added a comment - 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).

            People

              marko Marko Mäkelä
              marko Marko Mäkelä
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.