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

binlog_expire_logs_seconds doesn't allow documented maximum value

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Fixed
    • 10.11.10
    • N/A
    • Documentation
    • Debian 6.1, MariaDB 10.11.6

    Description

      The MariaDB documentation for "binlog_expire_logs_seconds" says:

      Range: 0 to 4294967295

      However trying to set to anything over 8553600 results in:

      Warning: Truncated incorrect binlog_expire_logs_seconds value

      ... and the value stays at 8553600. The documentation for the corresponding
      "expire_logs_days" variable says its maximum is 99 days, which is exactly 8553600 seconds. Either there's a bug that stops binlog_expire_logs_seconds going over 8553600 seconds (99 days), or the documentation is incorrect and it should be updated to show the correct maximum.

      Attachments

        Activity

          People

            serg Sergei Golubchik
            tobus Toby Chamberlain
            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.