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

innodb_max_purge_lag is documented as being in milliseconds, not microseconds

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • N/A
    • N/A
    • Documentation
    • None

    Description

      Via Marko:
      Related to MDEV-29401, Axel noted that innodb_max_purge_lag is documented as being in milliseconds, while in reality it is in microseconds.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-29401 InnoDB history list length increased in 10.6 compared to 10.5 for the same load

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

          Activity

            People

              greenman Ian Gilfillan
              greenman Ian Gilfillan
              Votes:
              0 Vote for this issue
              Watchers:
              1 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.