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

Unclear error with flashback: Variable 'binlog_format' can't be set to the value of 'statement'

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.2(EOL)
    • 10.2.6
    • Replication
    • None

    Description

      When flashback is enabled, the local value of binlog_format can still be set to STATEMENT or MIXED, and an informative warning is produced:

      MariaDB [test]> show warnings;
      +---------+------+------------------------------------------------------------------+
      | Level   | Code | Message                                                          |
      +---------+------+------------------------------------------------------------------+
      | Warning | 1105 | MariaDB Galera and flashback do not support binlog format: MIXED |
      +---------+------+------------------------------------------------------------------+
      1 row in set (0.01 sec)
      

      However, when one attempts to set the global value, it produces a generic error:

      MariaDB [test]> set global binlog_format=mixed;
      ERROR 1231 (42000): Variable 'binlog_format' can't be set to the value of 'mixed'
      

      Maybe there is a reason why a local value can be set and global can not, but then the error message should at least say why it is not possible, referring to flashback.

      Attachments

        Activity

          elenst Elena Stepanova created issue -
          elenst Elena Stepanova made changes -
          Field Original Value New Value
          Labels 10.2-ga
          sachin.setiya.007 Sachin Setiya (Inactive) made changes -
          Assignee Lixun Peng [ plinux ] Sachin Setiya [ sachin.setiya.007 ]
          sachin.setiya.007 Sachin Setiya (Inactive) made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          sachin.setiya.007 Sachin Setiya (Inactive) made changes -
          Assignee Sachin Setiya [ sachin.setiya.007 ] Michael Widenius [ monty ]
          Status In Progress [ 3 ] In Review [ 10002 ]
          elenst Elena Stepanova made changes -
          Labels 10.2-ga

          sachin.setiya.007, what's the state of it? where's the patch?

          serg Sergei Golubchik added a comment - sachin.setiya.007 , what's the state of it? where's the patch?
          serg Sergei Golubchik made changes -
          Assignee Michael Widenius [ monty ] Sergei Golubchik [ serg ]
          serg Sergei Golubchik made changes -
          Assignee Sergei Golubchik [ serg ] Sachin Setiya [ sachin.setiya.007 ]
          Status In Review [ 10002 ] Stalled [ 10000 ]
          sachin.setiya.007 Sachin Setiya (Inactive) made changes -
          Attachment patch [ 43587 ]
          sachin.setiya.007 Sachin Setiya (Inactive) added a comment - patch Pushed
          sachin.setiya.007 Sachin Setiya (Inactive) made changes -
          Fix Version/s 10.2.6 [ 22527 ]
          Fix Version/s 10.2 [ 14601 ]
          Resolution Fixed [ 1 ]
          Status Stalled [ 10000 ] Closed [ 6 ]
          serg Sergei Golubchik made changes -
          Workflow MariaDB v3 [ 79562 ] MariaDB v4 [ 151680 ]

          I'm having the same error reported when I try to set global binlog_format back to mixed.

          Why is that and how can I switch to mixed binlog format dynamically or is it required to restart server?

          ccounotte COUNOTTE CEDRIC added a comment - I'm having the same error reported when I try to set global binlog_format back to mixed. Why is that and how can I switch to mixed binlog format dynamically or is it required to restart server?

          People

            sachin.setiya.007 Sachin Setiya (Inactive)
            elenst Elena Stepanova
            Votes:
            0 Vote for this issue
            Watchers:
            5 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.