[MDEV-15994] VARIABLE_SCOPE and VARIABLE_COMMENT for SQL_LOG_BIN are outdated Created: 2018-04-23  Updated: 2023-04-27

Status: Open
Project: MariaDB Server
Component/s: Variables
Affects Version/s: 10.1, 10.2, 10.3
Fix Version/s: 10.4

Type: Bug Priority: Minor
Reporter: Elena Stepanova Assignee: Sergei Golubchik
Resolution: Unresolved Votes: 0
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.


Generated at Thu Feb 08 08:25:34 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.