Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-34860

Implement MAX_EXECUTION_TIME hint

    XMLWordPrintable

Details

    Description

      The hint limits the time of statement execution to the number of milliseconds given in the hint argument. The syntax is as follows:

      SELECT /*+ MAX_EXECUTION_TIME(milliseconds) */ ...

      Only top-level SELECT statements support the hint. Trying to apply it to INSERT, REPLACE, UPDATE and DELETE must issue a warning. The hint is not supported inside stored procedures, triggers, events and subqueries.

      Correctly handle situations where max_statement_time variable is set like here:

      SET STATEMENT max_statement_time=1 FOR
      		 
      SELECT /*+ MAX_EXECUTION_TIME(500) */ count(*) FROM t1 a;

      In this case a warning must be issued, and the hint MAX_EXECUTION_TIME must be ignored.

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. MDEV-35817 MAX_EXECUTION_TIME does not honor SLEEP(.5)

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-35822 UBSAN: UndefinedBehaviorSanitizer: function-type-mismatch in process_timers when using MAX_EXECUTION_TIME

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-35871 Query that runs for 2ms was not terminated when using MAX_EXECUTION_TIME(1)

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. MDEV-35880 Incorrect error message when MAX_EXECUTION_TIME was exceeded

          • Major - Major loss of function.
          • Confirmed
          is blocked by

          New Feature - A new feature of the product, which has yet to be developed. MDEV-34888 Implement subquery optimizer hints

          • Major - Major loss of function.
          • In Testing

          New Feature - A new feature of the product, which has yet to be developed. MDEV-35504 MySQL 8-style optimizer hints: milestone 1

          • Major - Major loss of function.
          • In Testing
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-35851 SIGSEGV in list_add on INSERT

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-33285 Assertion `m_table' failed in ha_perfschema::rnd_end on CHECKSUM TABLE

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-35483 Docs for optimizer hints

          • Major - Major loss of function.
          • Stalled

          Bug - A problem which impairs or prevents the functions of the product. MDEV-35819 Documentation: versions for Optimizer hints

          • Major - Major loss of function.
          • Confirmed
          split from

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. MDEV-33281 Implement optimizer hints like in MySQL 8

          • Critical - Crashes, loss of data, severe memory leak.
          • In Progress

          Activity

            People

              oleg.smirnov Oleg Smirnov
              oleg.smirnov Oleg Smirnov
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

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