Details

      Description

      https://travis-ci.org/grooverdan/mariadb-server/jobs/218041349#L4051

      ];mtr: spent 0:00:33 on 106 tests. 0:00:18 (60 tests) leftbinlog.binlog_unsafe 'stmt'              w4 [ fail ]
              Test ended at 2017-04-03 12:26:16
      CURRENT_TEST: binlog.binlog_unsafe
      mysqltest: At line 351: query '$CRC_RET_stmt_sidef' failed: 1406: Data too long for column 'a' at row 1
      The result from queries just before the failure was:
      < snip >
      Invoking statement that is unsafe in many ways.
      * binlog_format = STATEMENT: expect 7 warnings.
      INSERT DELAYED INTO double_autoinc_table SELECT CONCAT(UUID(), @@hostname, myfunc_int(), NULL) FROM mysql.general_log LIMIT 1;
      Warnings:
      Note	1592	Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted
      Note	1592	Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on slaves
      Note	1592	Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly
      Note	1592	Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a UDF which may not return the same value on the slave
      Note	1592	Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a system variable that may have a different value on the slave
      Note	1592	Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a system function that may return a different value on the slave
      Note	1592	Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave
      * SQL_LOG_BIN = 0: expect nothing logged and no warning.
      * binlog_format = MIXED: expect row events in binlog and no warning.
      ==== Testing a statement that is unsafe several times ====
      Invoking function func_sidef_1 invoking statement that is unsafe several times.
      CREATE FUNCTION func_sidef_1() RETURNS VARCHAR(100) BEGIN INSERT INTO ta1 VALUES (47); INSERT INTO ta0 VALUES (multi_unsafe_func()); RETURN 0; END;
      * binlog_format = STATEMENT: expect 2 warnings.
      INSERT INTO t1 SELECT func_sidef_1();
      More results from queries before failure can be found in /home/travis/build/grooverdan/mariadb-server/mysql-test/var/4/log/binlog_unsafe.log
       - saving '/home/travis/build/grooverdan/mariadb-server/mysql-test/var/4/log/binlog.binlog_unsafe-stmt/' to '/home/travis/build/grooverdan/mariadb-server/mysql-test/var/log/binlog.binlog_unsafe-stmt/'
      ];mtr: spent 0:00:33 on 107 tests. 0:00:18 (59 tests) left***Warnings generated in error logs during shutdown after running tests: binlog.binlog_unsafe
      2017-04-03 12:26:13 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a system function that may return a different value on the slave Statement: INSERT INTO t1 VALUES (func_retval_1())
      2017-04-03 12:26:13 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a system function that may return a different value on the slave Statement: SELECT func_retval_1()
      2017-04-03 12:26:13 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a system function that may return a different value on the slave Statement: INSERT INTO t2 VALUES (func_retval_2())
      2017-04-03 12:26:13 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a system function that may return a different value on the slave Statement: SELECT func_retval_2()
      2017-04-03 12:26:13 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a system function that may return a different value on the slave Statement: INSERT INTO t2 SELECT func_sidef_2()
      2017-04-03 12:26:13 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a system function that may return a different value on the slave Statement: CALL proc_2()
      2017-04-03 12:26:13 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a system function that may return a different value on the slave Statement: INSERT INTO trigger_table_2 VALUES (1)
      2017-04-03 12:26:13 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a system function that may return a different value on the slave Statement: CREATE VIEW view_retval_2 AS SELECT func_retval_1()
      2017-04-03 12:26:13 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a system function that may return a different value on the slave Statement: INSERT INTO t2 SELECT * FROM view_retval_2
      2017-04-03 12:26:13 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a system function that may return a different value on the slave Statement: SELECT * FROM view_retval_2
      2017-04-03 12:26:13 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a system variable that may have a different value on the slave Statement: INSERT INTO t1 VALUES (func_retval_1())
      2017-04-03 12:26:13 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a system variable that may have a different value on the slave Statement: SELECT func_retval_1()
      2017-04-03 12:26:13 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a system variable that may have a different value on the slave Statement: INSERT INTO t2 VALUES (func_retval_2())
      2017-04-03 12:26:13 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a system variable that may have a different value on the slave Statement: SELECT func_retval_2()
      2017-04-03 12:26:13 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a system variable that may have a different value on the slave Statement: INSERT INTO t2 SELECT func_sidef_2()
      2017-04-03 12:26:13 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a system variable that may have a different value on the slave Statement: CALL proc_2()
      2017-04-03 12:26:13 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a system variable that may have a different value on the slave Statement: INSERT INTO trigger_table_2 VALUES (1)
      2017-04-03 12:26:13 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a system variable that may have a different value on the slave Statement: CREATE VIEW view_retval_2 AS SELECT func_retval_1()
      2017-04-03 12:26:13 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a system variable that may have a different value on the slave Statement: INSERT INTO t2 SELECT * FROM view_retval_2
      2017-04-03 12:26:14 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted Statement: INSERT INTO t1 SELECT func_sidef_1()
      2017-04-03 12:26:14 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted Statement: INSERT INTO t2 SELECT func_sidef_2()
      2017-04-03 12:26:14 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted Statement: CALL proc_2()
      2017-04-03 12:26:14 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted Statement: INSERT INTO trigger_table_2 VALUES (1)
      2017-04-03 12:26:14 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted Statement: CREATE VIEW view_sidef_2 AS SELECT func_sidef_1()
      2017-04-03 12:26:14 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted Statement: INSERT INTO t2 SELECT * FROM view_sidef_2
      2017-04-03 12:26:14 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted Statement: INSERT INTO t1 SELECT func_sidef_1()
      2017-04-03 12:26:14 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted Statement: CALL proc_1()
      2017-04-03 12:26:14 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted Statement: INSERT INTO t2 SELECT func_sidef_2()
      2017-04-03 12:26:14 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly Statement: INSERT INTO t1 SELECT func_sidef_1()
      2017-04-03 12:26:14 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly Statement: INSERT INTO t2 SELECT func_sidef_2()
      2017-04-03 12:26:14 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly Statement: CALL proc_2()
      2017-04-03 12:26:14 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly Statement: INSERT INTO trigger_table_2 VALUES (1)
      2017-04-03 12:26:14 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly Statement: CREATE VIEW view_sidef_2 AS SELECT func_sidef_1()
      2017-04-03 12:26:14 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly Statement: INSERT INTO t2 SELECT * FROM view_sidef_2
      2017-04-03 12:26:14 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly Statement: INSERT INTO t1 SELECT func_sidef_1()
      2017-04-03 12:26:14 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly Statement: CALL proc_1()
      2017-04-03 12:26:14 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly Statement: INSERT INTO t2 SELECT func_sidef_2()
      2017-04-03 12:26:14 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a UDF which may not return the same value on the slave Statement: INSERT INTO t1 VALUES (func_retval_1())
      2017-04-03 12:26:14 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a UDF which may not return the same value on the slave Statement: SELECT func_retval_1()
      2017-04-03 12:26:14 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a UDF which may not return the same value on the slave Statement: INSERT INTO t2 VALUES (func_retval_2())
      2017-04-03 12:26:14 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a UDF which may not return the same value on the slave Statement: SELECT func_retval_2()
      2017-04-03 12:26:14 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a UDF which may not return the same value on the slave Statement: INSERT INTO t2 SELECT func_sidef_2()
      2017-04-03 12:26:14 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a UDF which may not return the same value on the slave Statement: CALL proc_2()
      2017-04-03 12:26:14 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a UDF which may not return the same value on the slave Statement: INSERT INTO trigger_table_2 VALUES (1)
      2017-04-03 12:26:14 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a UDF which may not return the same value on the slave Statement: CREATE VIEW view_retval_2 AS SELECT func_retval_1()
      2017-04-03 12:26:14 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a UDF which may not return the same value on the slave Statement: INSERT INTO t2 SELECT * FROM view_retval_2
      2017-04-03 12:26:14 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on slaves Statement: INSERT INTO t1 SELECT func_sidef_1()
      2017-04-03 12:26:14 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on slaves Statement: INSERT INTO t2 SELECT func_sidef_2()
      2017-04-03 12:26:14 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on slaves Statement: CALL proc_2()
      2017-04-03 12:26:14 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on slaves Statement: INSERT INTO trigger_table_2 VALUES (1)
      2017-04-03 12:26:14 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on slaves Statement: CREATE VIEW view_sidef_2 AS SELECT func_sidef_1()
      2017-04-03 12:26:15 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on slaves Statement: INSERT INTO t2 SELECT * FROM view_sidef_2
      2017-04-03 12:26:15 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on slaves Statement: INSERT INTO t1 SELECT func_sidef_1()
      2017-04-03 12:26:15 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on slaves Statement: CALL proc_1()
      2017-04-03 12:26:15 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on slaves Statement: INSERT INTO t2 SELECT func_sidef_2()
      2017-04-03 12:26:16 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave Statement: INSERT INTO t1 SELECT func_sidef_1()
      2017-04-03 12:26:16 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave Statement: INSERT INTO t2 SELECT func_sidef_2()
      2017-04-03 12:26:16 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave Statement: CALL proc_2()
      2017-04-03 12:26:16 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave Statement: INSERT INTO trigger_table_2 VALUES (1)
      2017-04-03 12:26:16 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave Statement: CREATE VIEW view_sidef_2 AS SELECT func_sidef_1()
      2017-04-03 12:26:16 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave Statement: INSERT INTO t2 SELECT * FROM view_sidef_2
      2017-04-03 12:26:16 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave Statement: INSERT INTO t1 SELECT func_sidef_1()
      2017-04-03 12:26:16 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave Statement: CALL proc_1()
      2017-04-03 12:26:16 140285110904576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave Statement: INSERT INTO t2 SELECT func_sidef_2()
      

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                elenst Elena Stepanova
                Reporter:
                danblack Daniel Black
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: