Replication and Binary Logging Options and Variables Holds the base name and path for the binary log index file, which can be set with the  --log-bin- index  server option. The maximum variable length is 256. This variable applies when binary logging is enabled. It controls whether stored function creators can be trusted not to create stored functions that may cause unsafe events to be written to the binary log. If set to 0 (the default), users are not permitted to create or alter stored functions unless they have the  SUPER privilege in addition to the  CREATE ROUTINE  or  ALTER ROUTINE  privilege. A setting of 0 also enforces the restriction that a function must be declared with the  DETERMINISTIC  characteristic, or with the READS SQL DATA  or  NO SQL  characteristic. If the variable is set to 1, MySQL does not enforce these restrictions on stored function creation. This variable also applies to trigger creation. See Section 25.7, “Stored Program Binary Logging” . This read-only system variable is deprecated. Setting the system variable to  ON  at server startup enabled row-based replication with replicas running MySQL Server 5.5 and earlier by writing the binary log using Version 1 binary log row events, instead of Version 2 binary log row events which are the default as of MySQL 5.6. • log_slave_updates • log_bin_use_v1_row_events • log_bin_trust_function_creators Dynamic No SET_VAR  Hint Applies No Type File name Command-Line Format --log-bin-trust-function- creators[={OFF|ON}] System Variable log_bin_trust_function_creators Scope Global Dynamic Yes SET_VAR  Hint Applies No Type Boolean Default Value OFF Command-Line Format --log-bin-use-v1-row-events[={OFF| ON}] Deprecated 8.0.18 System Variable log_bin_use_v1_row_events Scope Global Dynamic Yes SET_VAR  Hint Applies No Type Boolean Default Value OFF Command-Line Format --log-slave-updates[={OFF|ON}] System Variable log_slave_updates 3564