Details
-
Bug
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
10.1, 10.2, 10.3
-
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.