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

VARIABLE_SCOPE and VARIABLE_COMMENT for SQL_LOG_BIN are outdated

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 10.1, 10.2, 10.3
    • Fix Version/s: 10.1, 10.2, 10.3
    • Component/s: Variables
    • Labels:
      None

      Description

      10.1 3d1ad2a5e852

      MariaDB [test]> select * from information_schema.system_variables where variable_name like 'sql_log_bin' \G
      *************************** 1. row ***************************
              VARIABLE_NAME: SQL_LOG_BIN
              SESSION_VALUE: ON
               GLOBAL_VALUE: ON
        GLOBAL_VALUE_ORIGIN: COMPILE-TIME
              DEFAULT_VALUE: ON
             VARIABLE_SCOPE: SESSION
              VARIABLE_TYPE: BOOLEAN
           VARIABLE_COMMENT: If set to 0 (1 is the default), no logging to the binary log is done for the client. Only clients with the SUPER privilege can update this variable. Can have unintended consequences if set globally, see SET SQL_LOG_BIN. Starting MariaDB 10.1.7, this variable does not affect the replication of events in a Galera cluster.
          NUMERIC_MIN_VALUE: NULL
          NUMERIC_MAX_VALUE: NULL
         NUMERIC_BLOCK_SIZE: NULL
            ENUM_VALUE_LIST: OFF,ON
                  READ_ONLY: NO
      COMMAND_LINE_ARGUMENT: NULL
      1 row in set (0.01 sec)
      

      In fact, SQL_LOG_BIN has long been session-only, hence wrong scope, and the warning in the comment is obsolete.

        Attachments

          Activity

            People

            • Assignee:
              serg Sergei Golubchik
              Reporter:
              elenst Elena Stepanova
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: