rm -rf 89696 scripts/mysql_install_db --basedir=$PWD --datadir=$PWD/89696 -v bin/mysqld --no-defaults --basedir=$PWD --datadir=$PWD/89696 --core-file --socket=/tmp/mysql_ushastry.sock --port=3307 --log-error=$PWD/89696/log.err --log-bin --server-id=51 --event-scheduler --binlog_format=statement --log-warnings=0 2>&1 & -- [umshastr@hod03]/export/umesh/server/binaries/GABuilds/mysql-5.6.39: bin/mysql -uroot -S /tmp/mysql_ushastry.sock Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 2 Server version: 5.6.39-log MySQL Community Server (GPL) Copyright (c) 2000, 2018, Oracle and/or its affiliates. All rights reserved. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. mysql> create database test;create table test.t (c int);create table test.t1(c int);insert into test.t1 values (1),(2),(3),(4),(5);create event test.e1 on schedule every 1 minute starts current_timestamp + interval 1 minute do replace into t select * from t1; Query OK, 0 rows affected (0.01 sec) Query OK, 0 rows affected (0.00 sec) Query OK, 5 rows affected (0.00 sec) Records: 5 Duplicates: 0 Warnings: 0 Query OK, 0 rows affected (0.00 sec) mysql> show variables like 'log%'; +----------------------------------------+---------------------------------------------------------------------------+ | Variable_name | Value | +----------------------------------------+---------------------------------------------------------------------------+ | log_bin | ON | | log_bin_basename | /export/umesh/server/binaries/GABuilds/mysql-5.6.39/89696/hod03-bin | | log_bin_index | /export/umesh/server/binaries/GABuilds/mysql-5.6.39/89696/hod03-bin.index | | log_bin_trust_function_creators | OFF | | log_bin_use_v1_row_events | OFF | | log_error | /export/umesh/server/binaries/GABuilds/mysql-5.6.39/89696/log.err | | log_output | FILE | | log_queries_not_using_indexes | OFF | | log_slave_updates | OFF | | log_slow_admin_statements | OFF | | log_slow_slave_statements | OFF | | log_throttle_queries_not_using_indexes | 0 | | log_warnings | 0 | +----------------------------------------+---------------------------------------------------------------------------+ 13 rows in set (0.00 sec) -- error log is flooded with 'Note' [umshastr@hod03]/export/umesh/server/binaries/GABuilds/mysql-5.6.39: tail -f 89696/log.err 2018-02-21 07:46:28 15991 [Note] InnoDB: 5.6.39 started; log sequence number 1625987 2018-02-21 07:46:28 15991 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: f187915d-16d2-11e8-b25a-0010e05f3e06. 2018-02-21 07:46:28 15991 [Note] Server hostname (bind-address): '*'; port: 3307 2018-02-21 07:46:28 15991 [Note] IPv6 is available. 2018-02-21 07:46:28 15991 [Note] - '::' resolves to '::'; 2018-02-21 07:46:28 15991 [Note] Server socket created on IP: '::'. 2018-02-21 07:46:28 15991 [Note] Event Scheduler: Loaded 0 events 2018-02-21 07:46:28 15991 [Note] bin/mysqld: ready for connections. Version: '5.6.39-log' socket: '/tmp/mysql_ushastry.sock' port: 3307 MySQL Community Server (GPL) 2018-02-21 07:46:28 15991 [Note] Event Scheduler: scheduler thread started with id 1 2018-02-21 07:48:05 15991 [Note] Event Scheduler: [root@localhost][test.e1] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. 2018-02-21 07:49:05 15991 [Note] Event Scheduler: [root@localhost][test.e1] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. 2018-02-21 07:50:05 15991 [Note] Event Scheduler: [root@localhost][test.e1] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. 2018-02-21 07:51:05 15991 [Note] Event Scheduler: [root@localhost][test.e1] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. 2018-02-21 07:52:05 15991 [Note] Event Scheduler: [root@localhost][test.e1] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. 2018-02-21 07:53:05 15991 [Note] Event Scheduler: [root@localhost][test.e1] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. 2018-02-21 07:54:05 15991 [Note] Event Scheduler: [root@localhost][test.e1] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. 2018-02-21 07:55:05 15991 [Note] Event Scheduler: [root@localhost][test.e1] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. 2018-02-21 07:56:05 15991 [Note] Event Scheduler: [root@localhost][test.e1] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. 2018-02-21 07:57:05 15991 [Note] Event Scheduler: [root@localhost][test.e1] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. 2018-02-21 07:58:05 15991 [Note] Event Scheduler: [root@localhost][test.e1] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. 2018-02-21 07:59:05 15991 [Note] Event Scheduler: [root@localhost][test.e1] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. 2018-02-21 08:00:05 15991 [Note] Event Scheduler: [root@localhost][test.e1] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. 2018-02-21 08:01:05 15991 [Note] Event Scheduler: [root@localhost][test.e1] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. 2018-02-21 08:02:05 15991 [Note] Event Scheduler: [root@localhost][test.e1] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. 2018-02-21 08:03:05 15991 [Note] Event Scheduler: [root@localhost][test.e1] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. 2018-02-21 08:04:05 15991 [Note] Event Scheduler: [root@localhost][test.e1] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. 2018-02-21 08:05:05 15991 [Note] Event Scheduler: [root@localhost][test.e1] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. 2018-02-21 08:06:05 15991 [Note] Event Scheduler: [root@localhost][test.e1] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. 2018-02-21 08:07:05 15991 [Note] Event Scheduler: [root@localhost][test.e1] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. 2018-02-21 08:08:05 15991 [Note] Event Scheduler: [root@localhost][test.e1] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. 2018-02-21 08:09:05 15991 [Note] Event Scheduler: [root@localhost][test.e1] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. 2018-02-21 08:10:05 15991 [Note] Event Scheduler: [root@localhost][test.e1] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. 2018-02-21 08:11:05 15991 [Note] Event Scheduler: [root@localhost][test.e1] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. 2018-02-21 08:12:05 15991 [Note] Event Scheduler: [root@localhost][test.e1] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. 2018-02-21 08:13:05 15991 [Note] Event Scheduler: [root@localhost][test.e1] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. 2018-02-21 08:14:05 15991 [Note] Event Scheduler: [root@localhost][test.e1] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. 2018-02-21 08:15:05 15991 [Note] Event Scheduler: [root@localhost][test.e1] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. -- Setting log_warnings=0 is equivalent to log_error_verbosity=1 (errors only) rm -rf 89696 bin/mysqld --initialize-insecure --basedir=$PWD --datadir=$PWD/89696 -v bin/mysqld --no-defaults --basedir=$PWD --datadir=$PWD/89696 --core-file --socket=/tmp/mysql_ushastry.sock --port=3307 --log-error=$PWD/89696/log.err --log-bin --server-id=51 --event-scheduler --binlog_format=statement --log_error_verbosity=1 2>&1 & [umshastr@hod03]/export/umesh/server/binaries/GABuilds/mysql-5.7.21: bin/mysql -uroot -S /tmp/mysql_ushastry.sock Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 3 Server version: 5.7.21-log MySQL Community Server (GPL) Copyright (c) 2000, 2018, Oracle and/or its affiliates. All rights reserved. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. mysql> show variables like 'log%'; +----------------------------------------+---------------------------------------------------------------------------+ | Variable_name | Value | +----------------------------------------+---------------------------------------------------------------------------+ | log_bin | ON | | log_bin_basename | /export/umesh/server/binaries/GABuilds/mysql-5.7.21/89696/hod03-bin | | log_bin_index | /export/umesh/server/binaries/GABuilds/mysql-5.7.21/89696/hod03-bin.index | | log_bin_trust_function_creators | OFF | | log_bin_use_v1_row_events | OFF | | log_builtin_as_identified_by_password | OFF | | log_error | /export/umesh/server/binaries/GABuilds/mysql-5.7.21/89696/log.err | | log_error_verbosity | 1 | | log_output | FILE | | log_queries_not_using_indexes | OFF | | log_slave_updates | OFF | | log_slow_admin_statements | OFF | | log_slow_slave_statements | OFF | | log_statements_unsafe_for_binlog | ON | | log_syslog | OFF | | log_syslog_facility | daemon | | log_syslog_include_pid | ON | | log_syslog_tag | | | log_throttle_queries_not_using_indexes | 0 | | log_timestamps | UTC | | log_warnings | 0 | +----------------------------------------+---------------------------------------------------------------------------+ 21 rows in set (0.01 sec) mysql> create database test;create table test.t (c int);create table test.t1(c int);insert into test.t1 values (1),(2),(3),(4),(5);create event test.e1 on schedule every 1 minute starts current_timestamp + interval 1 minute do replace into t select * from t1; Query OK, 1 row affected (0.00 sec) Query OK, 0 rows affected (0.01 sec) Query OK, 0 rows affected (0.00 sec) Query OK, 5 rows affected (0.01 sec) Records: 5 Duplicates: 0 Warnings: 0 Query OK, 0 rows affected (0.00 sec) mysql> -- tail from error log [umshastr@hod03]/export/umesh/server/binaries/GABuilds/mysql-5.7.21: tail -f 89696/log.err ^^ all blank As expected - If I set log_error_verbosity=3 (errors, warnings, notes) then Note is logged. mysql> set global log_error_verbosity=3; Query OK, 0 rows affected (0.00 sec) [umshastr@hod03]/export/umesh/server/binaries/GABuilds/mysql-5.7.21: tail -f 89696/log.err 2018-02-21T07:46:58.222363Z 32 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. Statement: CREATE PROCEDURE `e1`() SQL SECURITY INVOKER replace into t select * from t1 2018-02-21T07:46:58.222411Z 32 [Note] Event Scheduler: [root@localhost][test.e1] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. 2018-02-21T07:47:58.221893Z 33 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. Statement: CREATE PROCEDURE `e1`() SQL SECURITY INVOKER replace into t select * from t1 2018-02-21T07:47:58.221929Z 33 [Note] Event Scheduler: [root@localhost][test.e1] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. 2018-02-21T07:48:58.221839Z 34 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. Statement: CREATE PROCEDURE `e1`() SQL SECURITY INVOKER replace into t select * from t1 2018-02-21T07:48:58.221868Z 34 [Note] Event Scheduler: [root@localhost][test.e1] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. 2018-02-21T07:49:58.222817Z 35 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. Statement: CREATE PROCEDURE `e1`() SQL SECURITY INVOKER replace into t select * from t1 2018-02-21T07:49:58.222856Z 35 [Note] Event Scheduler: [root@localhost][test.e1] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. 2018-02-21T07:50:58.222658Z 36 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. Statement: CREATE PROCEDURE `e1`() SQL SECURITY INVOKER replace into t select * from t1 2018-02-21T07:50:58.222693Z 36 [Note] Event Scheduler: [root@localhost][test.e1] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. 2018-02-21T07:51:58.223129Z 37 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. Statement: CREATE PROCEDURE `e1`() SQL SECURITY INVOKER replace into t select * from t1 2018-02-21T07:51:58.223179Z 37 [Note] Event Scheduler: [root@localhost][test.e1] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave.