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

mysqldump: unknown variable 'max-statement-time' when included via --defaults-file or --defaults-extra-file

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Duplicate
    • Affects Version/s: 10.8.3
    • Fix Version/s: N/A
    • Component/s: Scripts & Clients
    • Labels:
      None

      Description

      mariadb-dump --help includes:

      The following groups are read: mysqldump mariadb-dump client client-server client-mariadb
      The following specify which files/extra groups are read (specified before remaining options):
      --defaults-file=#         Only read default options from the given file #.
      --defaults-extra-file=#   Read this file after the global files are read.
      

      The documentation for max_statement_time indicates it can be set dynamically for a session.

      However attempts to set this variable in any of the listed groups result in 'unknown variable' error:

      eg

      root@ubuntu-server~# cat custom.cnf
       
      [mysqldump]
      max_statement_time = 0
       
      root@ubuntu-server~# mysqldump --defaults-extra-file=custom.cnf my_database >/dev/null
      mysqldump: unknown variable 'max_execution_time=0'
      

      Where the client and server are hosted on different servers and the user lacks SUPER, I'm not aware of any workaround available.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              Andrew Ryan Andrew Ryan
              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.