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

SET STATEMENT wait_timeout or interactive_timeout seem meaningless

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Trivial
    • Resolution: Won't Fix
    • Affects Version/s: N/A
    • Fix Version/s: 10.1.5
    • Component/s: OTHER
    • Labels:
      None

      Description

      Technically I can't say that SET STATEMENT wait_timeout = .. has no effect, but it looks pointless because how can there be inactivity if we are already executing the statement?

      Same is true for interactive_timeout.

      I didn't file this for Percona, but these variables are allowed in their SET STATEMENT too.

        Attachments

          Issue Links

          relates to

          Task - A task that needs to be done. MDEV-5231 Per query variables from Percona Server [patch]

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

          Technical task - A technical task. MDEV-6923 Testing for SET STATEMENT .. FOR (MDEV-5231, per-query variables)

          • Major - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              sanja Oleksandr Byelkin
              Reporter:
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              3 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.