Linux ip-172-26-2-223 5.4.0-1018-aws #18-Ubuntu SMP Wed Jun 24 01:15:00 UTC 2020 x86_64
Apache
: 172.26.2.223 | : 18.221.248.199
Cant Read [ /etc/named.conf ]
8.1.13
www
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
CREATE WP USER
BLACK DEFEND!
README
+ Create Folder
+ Create File
/
www /
server /
mysql /
mysql-test /
suite /
binlog /
t /
[ HOME SHELL ]
Name
Size
Permission
Action
binlog_anonymous_ownership.tes...
11.78
KB
-rw-r--r--
binlog_bug23533.test
1.48
KB
-rw-r--r--
binlog_bug36391-master.opt
32
B
-rw-r--r--
binlog_bug36391.test
1.18
KB
-rw-r--r--
binlog_cache_write_failure-mas...
97
B
-rw-r--r--
binlog_cache_write_failure.tes...
5.4
KB
-rw-r--r--
binlog_check_flush_log_asserti...
1.68
KB
-rw-r--r--
binlog_checksum.test
1.08
KB
-rw-r--r--
binlog_crash_safe_master_check...
51
B
-rw-r--r--
binlog_crash_safe_master_check...
2.6
KB
-rw-r--r--
binlog_database.test
370
B
-rw-r--r--
binlog_delete_and_flush_index....
3.53
KB
-rw-r--r--
binlog_dmls_on_tmp_tables_read...
2.38
KB
-rw-r--r--
binlog_drop_if_exists.test
3.47
KB
-rw-r--r--
binlog_drop_temp_table_on_disc...
2
KB
-rw-r--r--
binlog_drop_temp_table_on_disc...
1.75
KB
-rw-r--r--
binlog_enforce_gtid_consistenc...
379
B
-rw-r--r--
binlog_enforce_gtid_consistenc...
378
B
-rw-r--r--
binlog_enforce_gtid_consistenc...
1.46
KB
-rw-r--r--
binlog_enforce_gtid_consistenc...
3.75
KB
-rw-r--r--
binlog_enforce_gtid_consistenc...
314
B
-rw-r--r--
binlog_enforce_gtid_consistenc...
313
B
-rw-r--r--
binlog_enforce_gtid_consistenc...
739
B
-rw-r--r--
binlog_enforce_gtid_consistenc...
409
B
-rw-r--r--
binlog_error_action-master.opt
88
B
-rw-r--r--
binlog_error_action.test
17.12
KB
-rw-r--r--
binlog_flush_logs_error.test
1.72
KB
-rw-r--r--
binlog_foreign_key_parent_tabl...
44
B
-rw-r--r--
binlog_foreign_key_parent_tabl...
1.08
KB
-rw-r--r--
binlog_format_switch_in_tmp_ta...
2.77
KB
-rw-r--r--
binlog_grant.test
1.83
KB
-rw-r--r--
binlog_grant_alter_user-master...
32
B
-rw-r--r--
binlog_grant_alter_user.test
39.59
KB
-rw-r--r--
binlog_group_commit_flush_cras...
51
B
-rw-r--r--
binlog_group_commit_flush_cras...
2.17
KB
-rw-r--r--
binlog_group_commit_gtid_order...
4.6
KB
-rw-r--r--
binlog_group_commit_indefinite...
1.51
KB
-rw-r--r--
binlog_group_commit_sync_delay...
1.84
KB
-rw-r--r--
binlog_group_commit_sync_delay...
1.23
KB
-rw-r--r--
binlog_group_commit_sync_no_de...
3.72
KB
-rw-r--r--
binlog_gtid_automatic_using_ro...
2.02
KB
-rw-r--r--
binlog_gtid_cache-master.opt
117
B
-rw-r--r--
binlog_gtid_cache.test
635
B
-rw-r--r--
binlog_gtid_errors-master.opt
149
B
-rw-r--r--
binlog_gtid_errors.test
9.1
KB
-rw-r--r--
binlog_gtid_exhausted-master.o...
77
B
-rw-r--r--
binlog_gtid_exhausted.test
3.3
KB
-rw-r--r--
binlog_gtid_implicit_commit.te...
121
B
-rw-r--r--
binlog_gtid_innodb.test
132
B
-rw-r--r--
binlog_gtid_mix_ok_packet_all_...
131
B
-rw-r--r--
binlog_gtid_mix_ok_packet_all_...
1.63
KB
-rw-r--r--
binlog_gtid_mix_response_packe...
99
B
-rw-r--r--
binlog_gtid_mix_response_packe...
1.82
KB
-rw-r--r--
binlog_gtid_mode_set_gtid_next...
4.66
KB
-rw-r--r--
binlog_gtid_mysqlbinlog_row.te...
197
B
-rw-r--r--
binlog_gtid_mysqlbinlog_row_in...
707
B
-rw-r--r--
binlog_gtid_mysqlbinlog_row_my...
661
B
-rw-r--r--
binlog_gtid_mysqlbinlog_start_...
444
B
-rw-r--r--
binlog_gtid_mysqldump.test
2.09
KB
-rw-r--r--
binlog_gtid_next_begin_caused_...
948
B
-rw-r--r--
binlog_gtid_next_partially_fai...
2.93
KB
-rw-r--r--
binlog_gtid_next_partially_fai...
9.45
KB
-rw-r--r--
binlog_gtid_next_single_stmt_t...
968
B
-rw-r--r--
binlog_gtid_next_temporary_tab...
2.73
KB
-rw-r--r--
binlog_gtid_next_xa.test
241
B
-rw-r--r--
binlog_gtid_ps_reprepare.test
6.56
KB
-rw-r--r--
binlog_gtid_purge_binlog_at_st...
3.72
KB
-rw-r--r--
binlog_gtid_rbr_only_flag.test
2.51
KB
-rw-r--r--
binlog_gtid_reset_consistency_...
2.61
KB
-rw-r--r--
binlog_gtid_row_ctype_ucs.test
265
B
-rw-r--r--
binlog_gtid_simple_recovery.te...
6
KB
-rw-r--r--
binlog_gtid_state_update_deadl...
2.62
KB
-rw-r--r--
binlog_gtid_stm_ctype_ucs.test
280
B
-rw-r--r--
binlog_gtid_unknown_xid.test
5.39
KB
-rw-r--r--
binlog_gtid_utils.test
3.56
KB
-rw-r--r--
binlog_gtids_table_gcov.test
2.86
KB
-rw-r--r--
binlog_implicit_commit.test
290
B
-rw-r--r--
binlog_incident.test
1.39
KB
-rw-r--r--
binlog_incident_ignore-master....
24
B
-rw-r--r--
binlog_incident_ignore.test
152
B
-rw-r--r--
binlog_index-master.opt
16
B
-rw-r--r--
binlog_index.test
16.86
KB
-rw-r--r--
binlog_innodb-master.opt
25
B
-rw-r--r--
binlog_innodb.test
139
B
-rw-r--r--
binlog_innodb_row.test
2.72
KB
-rw-r--r--
binlog_killed.test
9.71
KB
-rw-r--r--
binlog_killed_simulate-master....
39
B
-rw-r--r--
binlog_killed_simulate.test
2.7
KB
-rw-r--r--
binlog_max_extension.test
2.61
KB
-rw-r--r--
binlog_max_flush_queue_time_wa...
32
B
-rw-r--r--
binlog_max_flush_queue_time_wa...
850
B
-rw-r--r--
binlog_mixed_cache_stat.test
277
B
-rw-r--r--
binlog_mixed_load_data.test
535
B
-rw-r--r--
binlog_mts_logical_clock.test
2.35
KB
-rw-r--r--
binlog_mts_logical_clock_gtid....
318
B
-rw-r--r--
binlog_mysqlbinlog-cp932-maste...
23
B
-rw-r--r--
binlog_mysqlbinlog-cp932.test
1.11
KB
-rw-r--r--
binlog_mysqlbinlog_base64.test
2.64
KB
-rw-r--r--
binlog_mysqlbinlog_concat.test
4.28
KB
-rw-r--r--
binlog_mysqlbinlog_filter.test
2.07
KB
-rw-r--r--
binlog_mysqlbinlog_intvar.test
1.59
KB
-rw-r--r--
binlog_mysqlbinlog_raw.test
3.53
KB
-rw-r--r--
binlog_mysqlbinlog_rewrite_db....
6.58
KB
-rw-r--r--
binlog_mysqlbinlog_row.test
204
B
-rw-r--r--
binlog_mysqlbinlog_row_innodb....
714
B
-rw-r--r--
binlog_mysqlbinlog_row_myisam....
669
B
-rw-r--r--
binlog_mysqlbinlog_row_trans.t...
4.07
KB
-rw-r--r--
binlog_mysqlbinlog_start_stop....
452
B
-rw-r--r--
binlog_mysqlbinlog_start_stop_...
1.95
KB
-rw-r--r--
binlog_nogtid_mix_response_pac...
480
B
-rw-r--r--
binlog_noop_dml_with_readonly....
2.4
KB
-rw-r--r--
binlog_old_versions.test
5.22
KB
-rw-r--r--
binlog_purge_binary_logs_stall...
70
B
-rw-r--r--
binlog_purge_binary_logs_stall...
1.36
KB
-rw-r--r--
binlog_purge_binary_logs_to.te...
3.45
KB
-rw-r--r--
binlog_query_filter_rules-mast...
40
B
-rw-r--r--
binlog_query_filter_rules.test
855
B
-rw-r--r--
binlog_rbr_only_savepoint.test
2.83
KB
-rw-r--r--
binlog_reset_connection_not_re...
3.49
KB
-rw-r--r--
binlog_reset_master.test
996
B
-rw-r--r--
binlog_rewrite.test
2.99
KB
-rw-r--r--
binlog_rewrite_db_noleak.test
2.65
KB
-rw-r--r--
binlog_rewrite_order.test
1.07
KB
-rw-r--r--
binlog_rewrite_suppress_use.te...
2.25
KB
-rw-r--r--
binlog_rotate_bgc_sync.test
3.37
KB
-rw-r--r--
binlog_rotate_deadlock-master....
181
B
-rw-r--r--
binlog_rotate_deadlock.test
1.75
KB
-rw-r--r--
binlog_row_binlog-master.opt
55
B
-rw-r--r--
binlog_row_binlog.test
783
B
-rw-r--r--
binlog_row_cache_stat.test
274
B
-rw-r--r--
binlog_row_create_select_crash...
1.35
KB
-rw-r--r--
binlog_row_ctype_cp932.test
268
B
-rw-r--r--
binlog_row_ctype_ucs.test
272
B
-rw-r--r--
binlog_row_delete_all_rows.tes...
688
B
-rw-r--r--
binlog_row_drop_tbl.test
215
B
-rw-r--r--
binlog_row_drop_tmp_tbl.test
233
B
-rw-r--r--
binlog_row_innodb_stat-master....
26
B
-rw-r--r--
binlog_row_insert_select.test
708
B
-rw-r--r--
binlog_row_kill_create_select....
845
B
-rw-r--r--
binlog_row_mix_innodb_myisam-m...
97
B
-rw-r--r--
binlog_row_mix_innodb_myisam.t...
585
B
-rw-r--r--
binlog_row_mysqlbinlog_db_filt...
4.36
KB
-rw-r--r--
binlog_row_mysqlbinlog_verbose...
5.59
KB
-rw-r--r--
binlog_row_query_log_events.te...
942
B
-rw-r--r--
binlog_server_id.test
794
B
-rw-r--r--
binlog_server_start_options-ma...
54
B
-rw-r--r--
binlog_server_start_options.te...
1.14
KB
-rw-r--r--
binlog_set_gtid_mode_ongoing_t...
6.96
KB
-rw-r--r--
binlog_set_trans_dependency_de...
2.24
KB
-rw-r--r--
binlog_sf.test
2.67
KB
-rw-r--r--
binlog_shutdown_hang.test
1.14
KB
-rw-r--r--
binlog_simulate_crash_and_erro...
4.24
KB
-rw-r--r--
binlog_spurious_ddl_errors-mas...
20
B
-rw-r--r--
binlog_spurious_ddl_errors.tes...
4.16
KB
-rw-r--r--
binlog_sql_mode.test
4.75
KB
-rw-r--r--
binlog_start_comment.test
1.01
KB
-rw-r--r--
binlog_start_slave_heartbeat-s...
16
B
-rw-r--r--
binlog_start_slave_heartbeat.t...
1.33
KB
-rw-r--r--
binlog_stm_binlog-master.opt
55
B
-rw-r--r--
binlog_stm_binlog.test
741
B
-rw-r--r--
binlog_stm_blackhole.test
456
B
-rw-r--r--
binlog_stm_cache_stat.test
280
B
-rw-r--r--
binlog_stm_ctype_cp932.test
318
B
-rw-r--r--
binlog_stm_ctype_ucs.test
287
B
-rw-r--r--
binlog_stm_delete_all_rows.tes...
712
B
-rw-r--r--
binlog_stm_do_db-master.opt
38
B
-rw-r--r--
binlog_stm_do_db.test
2.8
KB
-rw-r--r--
binlog_stm_drop_tbl.test
230
B
-rw-r--r--
binlog_stm_drop_tmp_tbl.test
248
B
-rw-r--r--
binlog_stm_innodb_stat-master....
26
B
-rw-r--r--
binlog_stm_insert_select.test
489
B
-rw-r--r--
binlog_stm_mix_innodb_myisam-m...
145
B
-rw-r--r--
binlog_stm_mix_innodb_myisam.t...
552
B
-rw-r--r--
binlog_stm_ps.test
939
B
-rw-r--r--
binlog_stm_row.test
3.38
KB
-rw-r--r--
binlog_stm_unsafe_warning-mast...
51
B
-rw-r--r--
binlog_stm_unsafe_warning.test
5.65
KB
-rw-r--r--
binlog_stm_user_variables.test
3.4
KB
-rw-r--r--
binlog_switch_inside_trans.tes...
7.63
KB
-rw-r--r--
binlog_temporary_tables_user_v...
1.14
KB
-rw-r--r--
binlog_tmp_table.test
4.53
KB
-rw-r--r--
binlog_transaction_dependency_...
90
B
-rw-r--r--
binlog_transaction_dependency_...
8.21
KB
-rw-r--r--
binlog_transaction_dependency_...
2.2
KB
-rw-r--r--
binlog_transaction_write_set_s...
44
B
-rw-r--r--
binlog_transaction_write_set_s...
1.98
KB
-rw-r--r--
binlog_transaction_write_set_s...
44
B
-rw-r--r--
binlog_transaction_write_set_s...
1.33
KB
-rw-r--r--
binlog_transaction_write_set_s...
44
B
-rw-r--r--
binlog_transaction_write_set_s...
1.21
KB
-rw-r--r--
binlog_transaction_write_set_s...
44
B
-rw-r--r--
binlog_transaction_write_set_s...
4.15
KB
-rw-r--r--
binlog_truncate_kill.test
1.96
KB
-rw-r--r--
binlog_truncate_myisam.test
348
B
-rw-r--r--
binlog_unsafe-master.opt
65
B
-rw-r--r--
binlog_unsafe.test
25.95
KB
-rw-r--r--
binlog_unsafe_stmt_capable_eng...
41
B
-rw-r--r--
binlog_unsafe_stmt_capable_eng...
12.55
KB
-rw-r--r--
binlog_use_gtid_skip.test
1.03
KB
-rw-r--r--
binlog_user_if_exists.test
9.22
KB
-rw-r--r--
binlog_variables_log_bin-maste...
16
B
-rw-r--r--
binlog_variables_log_bin.test
136
B
-rw-r--r--
binlog_variables_log_bin_index...
70
B
-rw-r--r--
binlog_variables_log_bin_index...
136
B
-rw-r--r--
binlog_variables_log_statement...
2.18
KB
-rw-r--r--
binlog_wait_for_executed_gtid_...
879
B
-rw-r--r--
binlog_wait_for_executed_gtid_...
2.45
KB
-rw-r--r--
binlog_wait_for_executed_gtid_...
633
B
-rw-r--r--
binlog_wait_for_executed_gtid_...
801
B
-rw-r--r--
binlog_write_error.test
2.7
KB
-rw-r--r--
binlog_writeset_history_protec...
3.06
KB
-rw-r--r--
binlog_wrong_last_committed.te...
3.07
KB
-rw-r--r--
binlog_xa_handling.test
3.69
KB
-rw-r--r--
binlog_xa_modify_gtid_executed...
2.93
KB
-rw-r--r--
binlog_xa_prepare_failure.test
2.05
KB
-rw-r--r--
binlog_xa_prepared_disconnect....
628
B
-rw-r--r--
binlog_xa_rollback_failure.tes...
1.4
KB
-rw-r--r--
binlog_xa_select_gtid_executed...
2.41
KB
-rw-r--r--
binlog_xa_trx_gtid_response_pa...
98
B
-rw-r--r--
binlog_xa_trx_gtid_response_pa...
1.1
KB
-rw-r--r--
binlog_xa_trx_split_across_bin...
2.51
KB
-rw-r--r--
disabled.def
404
B
-rw-r--r--
log_builtin_as_identified_by_p...
39
B
-rw-r--r--
log_builtin_as_identified_by_p...
128
B
-rw-r--r--
show_binlog_events_no_lock.tes...
2.27
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : binlog_unsafe.test
# ==== Background ==== # # Some statements may execute differently on master and slave when # logged in statement format. Such statements are called unsafe. # Unsafe statements include: # # - statements using @@variables (with a small number of exceptions; # see below); # - statements using certain functions, e.g., UUID(); # - statements using LIMIT; # - insert into two autoinc columns; # - statements using UDF's. # - statements reading from log tables in the mysql database. # - INSERT ... SELECT ... ON DUPLICATE KEY UPDATE # - REPLACE ... SELECT # - CREATE TABLE [IGNORE/REPLACE] SELECT # - INSERT IGNORE...SELECT # - UPDATE IGNORE # - INSERT... ON DUPLICATE KEY UPDATE on a table with two UNIQUE KEYS # # Note that statements that use stored functions, stored procedures, # triggers, views, or prepared statements that invoke unsafe # statements shall also be unsafe. # # Unsafeness of a statement shall have the following consequences: # # 1. If the binlogging is on and the unsafe statement is logged: # - If binlog_format=STATEMENT, the statement shall give a warning. # - If binlog_format=MIXED or binlog_format=ROW, the statement shall # be logged in row format. # # 2. If binlogging is off or the statement is not logged (e.g. SELECT # UUID()), no warning shall be issued and the statement shall not # be logged. # # Moreover, when a sub-statement of a recursive construct (i.e., # stored function, stored procedure, trigger, view, or prepared # statement) is unsafe and binlog_format=STATEMENT, then a warning # shall be issued for every recursive construct. In effect, this # creates a stack trace from the top-level statement to the unsafe # statement. # # # ==== Purpose ==== # # This test verifies that a warning is generated when it should, # according to the rules above. # # All @@variables should be unsafe, with some exceptions. Therefore, # this test also verifies that the exceptions do *not* generate a # warning. # # # ==== Method ==== # # 1. Each type of statements listed above is executed. # # 2. Each unsafe statement is wrapped in each type of recursive # construct (stored function, stored procedure, trigger, view, or # prepared statement). # # 3. Each unsafe statement is wrapped in two levels of recursive # constructs (function invoking trigger invoking UUID(), etc). # # We try to insert the variables that should not be unsafe into a # table, and verify that *no* warning is issued. # # Execute a unsafe statement calling a trigger or stored function # or neither when SQL_LOG_BIN is turned ON, a warning/error should be issued # Execute a unsafe statement calling a trigger or stored function # or neither when @@SQL_LOG_BIN is turned OFF, # no warning/error is issued # # # ==== Related bugs and worklogs ==== # # WL#3339: Issue warnings when statement-based replication may fail # BUG#31168: @@hostname does not replicate # BUG#34732: mysqlbinlog does not print default values for auto_increment variables # BUG#34768: nondeterministic INSERT using LIMIT logged in stmt mode if binlog_format=mixed # BUG#41980, SBL, INSERT .. SELECT .. LIMIT = ERROR, even when @@SQL_LOG_BIN is 0 # BUG#42640: mysqld crashes when unsafe statements are executed (STRICT_TRANS_TABLES mode) # BUG#45785: LIMIT in SP does not cause RBL if binlog_format=MIXED # BUG#47995: Mark user functions as unsafe # BUG#49222: Mark RAND() unsafe # BUG#11758262: MARK INSERT...SEL...ON DUP KEY UPD,REPLACE...SEL,CREATE...[IGN|REPL] SEL # # ==== Related test cases ==== # # rpl.rpl_variables verifies that variables which cannot be replicated # safely in statement mode are replicated correctly in mixed or row # mode. # # rpl.rpl_variables_stm tests the small subset of variables that # actually can be replicated safely in statement mode. # # rpl_ndb.rpl_ndb_binlog_format_errors tests all errors and warnings # related to logging format (not just 'Unsafe statement written to the # binary log using statement format since BINLOG_FORMAT = STATEMENT'). --source include/have_udf.inc --source include/have_log_bin.inc --source include/have_binlog_format_statement.inc --source include/not_gtid_enabled.inc --disable_query_log call mtr.add_suppression("Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT"); --enable_query_log --echo #### Setup tables #### CREATE TABLE t0 (a CHAR(100)); CREATE TABLE t1 (a CHAR(100)); CREATE TABLE t2 (a CHAR(100)); CREATE TABLE t3 (a CHAR(100)); CREATE TABLE ta0 (a CHAR(100)); CREATE TABLE ta1 (a CHAR(100)); CREATE TABLE ta2 (a CHAR(100)); CREATE TABLE ta3 (a CHAR(100)); CREATE TABLE autoinc_table (a INT PRIMARY KEY AUTO_INCREMENT); CREATE TABLE data_table (a CHAR(100)); INSERT INTO data_table VALUES ('foo'); CREATE TABLE trigger_table_1 (a INT); CREATE TABLE trigger_table_2 (a INT); CREATE TABLE trigger_table_3 (a INT); CREATE TABLE double_autoinc_table (a INT PRIMARY KEY AUTO_INCREMENT); --DELIMITER | CREATE TRIGGER double_autoinc_trig BEFORE INSERT ON double_autoinc_table FOR EACH ROW BEGIN INSERT INTO autoinc_table VALUES (NULL); END| CREATE FUNCTION multi_unsafe_func() RETURNS INT BEGIN INSERT INTO t0 VALUES(CONCAT(@@hostname, @@hostname)); INSERT INTO t0 VALUES(0); INSERT INTO t0 VALUES(CONCAT(UUID(), @@hostname)); RETURN 1; END| --DELIMITER ; --replace_result $UDF_EXAMPLE_LIB UDF_EXAMPLE_LIB --eval CREATE FUNCTION myfunc_int RETURNS INTEGER SONAME "$UDF_EXAMPLE_LIB" # In each iteration of this loop, we select one method to make the # statement unsafe. --let $unsafe_type= 0 while ($unsafe_type < 8) { --echo if ($unsafe_type == 0) { --echo ==== Testing UUID() unsafeness ==== --let $desc_0= unsafe UUID() function --let $stmt_sidef_0= INSERT INTO t0 VALUES (UUID()) --let $value_0= UUID() --let $sel_sidef_0= --let $sel_retval_0= SELECT UUID() --let $CRC_ARG_expected_number_of_warnings= 1 --let $CRC_ARG_expected_number_of_deprecation_warnings= 0 } if ($unsafe_type == 1) { --echo ==== Testing @@hostname unsafeness ==== --let $desc_0= unsafe @@hostname variable --let $stmt_sidef_0= INSERT INTO t0 VALUES (@@hostname) --let $value_0= @@hostname --let $sel_sidef_0= # $sel_retval is going to be used in views. Views cannot execute # statements that refer to @@variables. Hence, we set $set_retval # to empty instead of SELECT @@hostname. --let $sel_retval_0= --let $CRC_ARG_expected_number_of_warnings= 1 --let $CRC_ARG_expected_number_of_deprecation_warnings= 0 } if ($unsafe_type == 2) { --echo ==== Testing SELECT...LIMIT unsafeness ==== --let $desc_0= unsafe SELECT...LIMIT statement --let $stmt_sidef_0= INSERT INTO t0 SELECT * FROM data_table LIMIT 1 --let $value_0= --let $sel_sidef_0= --let $sel_retval_0= SELECT * FROM data_table LIMIT 1 --let $CRC_ARG_expected_number_of_warnings= 1 --let $CRC_ARG_expected_number_of_deprecation_warnings= 0 } if ($unsafe_type == 3) { --echo ==== Testing unsafeness of insert of two autoinc values ==== --let $desc_0= unsafe update of two autoinc columns --let $stmt_sidef_0= INSERT INTO double_autoinc_table VALUES (NULL) --let $value_0= --let $sel_sidef_0= --let $sel_retval_0= --let $CRC_ARG_expected_number_of_warnings= 1 --let $CRC_ARG_expected_number_of_deprecation_warnings= 0 } if ($unsafe_type == 4) { --echo ==== Testing unsafeness of UDF's ==== --let $desc_0= unsafe UDF --let $stmt_sidef_0= INSERT INTO t0 VALUES (myfunc_int(10)) --let $value_0= myfunc_int(10) --let $sel_sidef_0= SELECT myfunc_int(10) --let $sel_retval_0= --let $CRC_ARG_expected_number_of_warnings= 1 --let $CRC_ARG_expected_number_of_deprecation_warnings= 0 } if ($unsafe_type == 5) { --echo ==== Testing unsafeness of access to mysql.general_log ==== --let $desc_0= unsafe use of mysql.general_log --let $stmt_sidef_0= INSERT INTO t0 SELECT COUNT(*) FROM mysql.general_log --let $value_0= --let $sel_sidef_0= --let $sel_retval_0= SELECT COUNT(*) FROM mysql.general_log --let $CRC_ARG_expected_number_of_warnings= 1 --let $CRC_ARG_expected_number_of_deprecation_warnings= 0 } if ($unsafe_type == 6) { --echo ==== Testing a statement that is unsafe in many ways ==== --let $desc_0= statement that is unsafe in many ways # Concatenate three unsafe values, and then concatenate NULL to # that so that the result is NULL and we instead use autoinc. --let $stmt_sidef_0= INSERT INTO double_autoinc_table SELECT CONCAT(UUID(), @@hostname, myfunc_int(), NULL) FROM mysql.general_log LIMIT 1 --let $value_0= --let $sel_sidef_0= --let $sel_retval_0= --let $CRC_ARG_expected_number_of_warnings= 7 --let $CRC_ARG_expected_number_of_deprecation_warnings= 1 } if ($unsafe_type == 7) { --echo ==== Testing a statement that is unsafe several times ==== --let $desc_0= statement that is unsafe several times --let $stmt_sidef_0= INSERT INTO ta0 VALUES (multi_unsafe_func()) --let $value_0= --let $sel_sidef_0= SELECT multi_unsafe_func() --let $sel_retval_0= --let $CRC_ARG_expected_number_of_warnings= 2 --let $CRC_ARG_expected_number_of_deprecation_warnings= 0 } # In each iteration of the following loop, we select one way to # enclose the unsafe statement as a sub-statement of a recursive # construct (i.e., a function, procedure, trigger, view, or prepared # statement). # # In the last iteration, $call_type_1=7, we don't create a recursive # construct. Instead, we just invoke the unsafe statement directly. --let $call_type_1= 0 while ($call_type_1 < 7) { #--echo debug: level 1, types $call_type_1 -> $unsafe_type --let $CRC_ARG_level= 1 --let $CRC_ARG_type= $call_type_1 --let $CRC_ARG_stmt_sidef= $stmt_sidef_0 --let $CRC_ARG_value= $value_0 --let $CRC_ARG_sel_sidef= $sel_sidef_0 --let $CRC_ARG_sel_retval= $sel_retval_0 --let $CRC_ARG_desc= $desc_0 --source extra/rpl_tests/create_recursive_construct.inc --let $stmt_sidef_1= $CRC_RET_stmt_sidef --let $value_1= $CRC_RET_value --let $sel_sidef_1= $CRC_RET_sel_sidef --let $sel_retval_1= $CRC_RET_sel_retval --let $is_toplevel_1= $CRC_RET_is_toplevel --let $drop_1= $CRC_RET_drop --let $desc_1= $CRC_RET_desc # Some statements must be top-level statements, i.e., cannot be # called as a sub-statement of any recursive construct. (One # example is 'EXECUTE prepared_stmt'). When # create_recursive_construct.inc creates a top-level statement, it # sets $CRC_RET_is_toplevel=1. if (!$is_toplevel_1) { # In each iteration of this loop, we select one way to enclose # the previous recursive construct in another recursive # construct. --let $call_type_2= 0 while ($call_type_2 < 6) { #--echo debug: level 2, types $call_type_2 -> $call_type_1 -> $unsafe_type --let $CRC_ARG_level= 2 --let $CRC_ARG_type= $call_type_2 --let $CRC_ARG_stmt_sidef= $stmt_sidef_1 --let $CRC_ARG_value= $value_1 --let $CRC_ARG_sel_sidef= $sel_sidef_1 --let $CRC_ARG_sel_retval= $sel_retval_1 --let $CRC_ARG_desc= $desc_1 --source extra/rpl_tests/create_recursive_construct.inc --let $stmt_sidef_2= $CRC_RET_stmt_sidef --let $value_2= $CRC_RET_value --let $sel_sidef_2= $CRC_RET_sel_sidef --let $sel_retval_2= $CRC_RET_sel_retval --let $is_toplevel_2= $CRC_RET_is_toplevel --let $drop_2= $CRC_RET_drop --let $desc_2= $CRC_RET_desc if (!$is_toplevel_2) { # Conditioned out since it makes result file really big. if (0) { # In each iteration of this loop, we select one way to enclose # the previous recursive construct in another recursive # construct. --let $call_type_3= 0 while ($call_type_3 < 6) { #--echo debug: level 3, types $call_type_2 -> $call_type_2 -> $call_type_1 -> $unsafe_type --let $CRC_ARG_level= 3 --let $CRC_ARG_type= $call_type_3 --let $CRC_ARG_stmt_sidef= $stmt_sidef_2 --let $CRC_ARG_value= $value_2 --let $CRC_ARG_sel_sidef= $sel_sidef_2 --let $CRC_ARG_sel_retval= $sel_retval_2 --let $CRC_ARG_desc= $desc_2 --source extra/rpl_tests/create_recursive_construct.inc # Drop created object. if ($drop_3) { --eval $drop_3 } --inc $call_type_3 } # while (call_type_3) } # if (0) } # if (!is_toplevel_2) # Drop created object. if ($drop_2) { --eval $drop_2 } --inc $call_type_2 } # while (call_type_2) } # if (!is_toplevel_1) # Drop created object. if ($drop_1) { --eval $drop_1 } --inc $call_type_1 } # while (call_type_1) --inc $unsafe_type } # while (unsafe_type) DROP TRIGGER double_autoinc_trig; DROP TABLE t0, t1, t2, t3, ta0, ta1, ta2, ta3, autoinc_table, double_autoinc_table, data_table, trigger_table_1, trigger_table_2, trigger_table_3; DROP FUNCTION myfunc_int; DROP FUNCTION multi_unsafe_func; --echo ==== Special system variables that should *not* be unsafe ==== CREATE TABLE t1 (a VARCHAR(1000)); CREATE TABLE autoinc_table (a INT PRIMARY KEY AUTO_INCREMENT); INSERT INTO t1 VALUES (@@session.auto_increment_increment); INSERT INTO t1 VALUES (@@session.auto_increment_offset); INSERT INTO t1 VALUES (@@session.character_set_client); INSERT INTO t1 VALUES (@@session.character_set_connection); INSERT INTO t1 VALUES (@@session.character_set_database); INSERT INTO t1 VALUES (@@session.character_set_server); INSERT INTO t1 VALUES (@@session.collation_connection); INSERT INTO t1 VALUES (@@session.collation_database); INSERT INTO t1 VALUES (@@session.collation_server); INSERT INTO t1 VALUES (@@session.foreign_key_checks); INSERT INTO t1 VALUES (@@session.identity); INSERT INTO t1 VALUES (@@session.last_insert_id); INSERT INTO t1 VALUES (@@session.lc_time_names); INSERT INTO t1 VALUES (@@session.pseudo_thread_id); INSERT INTO t1 VALUES (@@session.sql_auto_is_null); INSERT INTO t1 VALUES (@@session.timestamp); INSERT INTO t1 VALUES (@@session.time_zone); INSERT INTO t1 VALUES (@@session.unique_checks); SET @my_var= 4711; INSERT INTO t1 VALUES (@my_var); # using insert_id implicitly should be ok. SET insert_id= 12; INSERT INTO autoinc_table VALUES (NULL); # See set_var.cc for explanation. --echo The following variables *should* give a warning, despite they are replicated. INSERT INTO t1 VALUES (@@session.sql_mode); INSERT INTO t1 VALUES (@@session.insert_id); DROP TABLE t1, autoinc_table; # # BUG#34768 - nondeterministic INSERT using LIMIT logged in stmt mode if # binlog_format=mixed # CREATE TABLE t1(a INT, b INT, KEY(a), PRIMARY KEY(b)); INSERT INTO t1 SELECT * FROM t1 LIMIT 1; REPLACE INTO t1 SELECT * FROM t1 LIMIT 1; UPDATE t1 SET a=1 LIMIT 1; DELETE FROM t1 LIMIT 1; delimiter |; CREATE PROCEDURE p1() BEGIN INSERT INTO t1 SELECT * FROM t1 LIMIT 1; REPLACE INTO t1 SELECT * FROM t1 LIMIT 1; UPDATE t1 SET a=1 LIMIT 1; DELETE FROM t1 LIMIT 1; END| delimiter ;| CALL p1(); DROP PROCEDURE p1; DROP TABLE t1; # # Bug#42634: % character in query can cause mysqld signal 11 segfault # --disable_warnings DROP TABLE IF EXISTS t1; --enable_warnings CREATE TABLE t1 (a VARCHAR(100), b VARCHAR(100)); INSERT INTO t1 VALUES ('a','b'); UPDATE t1 SET b = '%s%s%s%s%s%s%s%s%s%s%s%s%s%s' WHERE a = 'a' LIMIT 1; DROP TABLE t1; # #For bug#41980, SBL, INSERT .. SELECT .. LIMIT = ERROR, even when @@SQL_LOG_BIN is 0 # --disable_warnings DROP TABLE IF EXISTS t1, t2; --enable_warnings CREATE TABLE t1(i INT PRIMARY KEY); CREATE TABLE t2(i INT PRIMARY KEY); CREATE TABLE t3(i INT, ch CHAR(50)); --echo "Should issue message Statement may not be safe to log in statement format." INSERT INTO t1 SELECT * FROM t2 LIMIT 1; DELIMITER |; CREATE FUNCTION func6() RETURNS INT BEGIN INSERT INTO t1 VALUES (10); INSERT INTO t1 VALUES (11); INSERT INTO t1 VALUES (12); RETURN 0; END| DELIMITER ;| --echo "Should issue message Statement may not be safe to log in statement format only once" INSERT INTO t3 VALUES(func6(), UUID()); --echo "Check whether SET @@SQL_LOG_BIN = 0/1 doesn't work in substatements" DELIMITER |; CREATE FUNCTION fun_check_log_bin() RETURNS INT BEGIN SET @@SQL_LOG_BIN = 0; INSERT INTO t1 VALUES(@@global.sync_binlog); RETURN 100; END| DELIMITER ;| --echo "One unsafe warning should be issued in the following statement" --error ER_STORED_FUNCTION_PREVENTS_SWITCH_SQL_LOG_BIN SELECT fun_check_log_bin(); --echo "SQL_LOG_BIN should be ON still" SHOW VARIABLES LIKE "SQL_LOG_BIN"; set @save_log_bin = @@SESSION.SQL_LOG_BIN; set @@SESSION.SQL_LOG_BIN = 0; --echo "Should NOT have any warning message issued in the following statements" INSERT INTO t1 SELECT * FROM t2 LIMIT 1; DROP TABLE t1,t2; --echo "Should NOT have any warning message issued in the following func7() and trig" CREATE TABLE t1 (a INT); CREATE TABLE t2 (a TEXT); CREATE TABLE trigger_table (a CHAR(7)); DELIMITER |; CREATE FUNCTION func7() RETURNS INT BEGIN INSERT INTO t1 VALUES (@@global.sync_binlog); INSERT INTO t1 VALUES (@@session.insert_id); INSERT INTO t2 SELECT UUID(); INSERT INTO t2 VALUES (@@session.sql_mode); INSERT INTO t2 VALUES (@@global.init_slave); RETURN 0; END| DELIMITER ;| SHOW VARIABLES LIKE "SQL_LOG_BIN"; SELECT func7(); --echo ---- Insert from trigger ---- DELIMITER |; CREATE TRIGGER trig BEFORE INSERT ON trigger_table FOR EACH ROW BEGIN INSERT INTO t1 VALUES (@@global.sync_binlog); INSERT INTO t1 VALUES (@@session.insert_id); INSERT INTO t1 VALUES (@@global.auto_increment_increment); INSERT INTO t2 SELECT UUID(); INSERT INTO t2 VALUES (@@session.sql_mode); INSERT INTO t2 VALUES (@@global.init_slave); INSERT INTO t2 VALUES (@@hostname); END| DELIMITER ;| INSERT INTO trigger_table VALUES ('bye.'); #clean up DROP FUNCTION fun_check_log_bin; DROP FUNCTION func6; DROP FUNCTION func7; DROP TRIGGER trig; DROP TABLE t1, t2, t3, trigger_table; set @@SESSION.SQL_LOG_BIN = @save_log_bin; # # For BUG#42640: mysqld crashes when unsafe statements are executed (STRICT_TRANS_TABLES mode) # SET @save_sql_mode = @@SESSION.SQL_MODE; SET @@SESSION.SQL_MODE = STRICT_ALL_TABLES; CREATE TABLE t1(i INT PRIMARY KEY); CREATE TABLE t2(i INT PRIMARY KEY); INSERT INTO t1 SELECT * FROM t2 LIMIT 1; INSERT INTO t1 VALUES(@@global.sync_binlog); UPDATE t1 SET i = 999 LIMIT 1; DELETE FROM t1 LIMIT 1; DROP TABLE t1, t2; SET @@SESSION.SQL_MODE = @save_sql_mode; # # BUG#45785: LIMIT in SP does not cause RBL if binlog_format=MIXED # SET @old_binlog_format = @@session.binlog_format; SET binlog_format = MIXED; CREATE TABLE t1 (a INT); CREATE TABLE t2 (a INT); INSERT INTO t2 VALUES (1), (2); --DELIMITER | CREATE FUNCTION func_limit () RETURNS INT BEGIN INSERT INTO t1 SELECT * FROM t2 LIMIT 1; RETURN 1; END| --DELIMITER ; RESET MASTER; SELECT func_limit(); --let $mask_binlog_commit_events= 1 source include/show_binlog_events.inc; --let $mask_binlog_commit_events= 0 SET @@session.binlog_format = @old_binlog_format; DROP TABLE t1, t2; DROP FUNCTION func_limit; # # BUG#45827 # The test verifies if stmt that have more than one # different tables to update with autoinc columns # will produce unsafe warning # # Test case1: stmt that have more than one different tables # to update with autoinc columns should produce # unsafe warning when calling a function CREATE TABLE t1 (a INT, b INT PRIMARY KEY AUTO_INCREMENT); CREATE TABLE t2 (a INT, b INT PRIMARY KEY AUTO_INCREMENT); # The purpose of this function is to insert into t1 so that the second # column is auto_increment'ed. DELIMITER |; CREATE FUNCTION func_modify_t1 () RETURNS INT BEGIN INSERT INTO t1 SET a = 1; RETURN 0; END| DELIMITER ;| --echo # The following statement causes auto-incrementation --echo # of both t1 and t2. It is logged in statement format, --echo # so it should produce unsafe warning. INSERT INTO t2 SET a = func_modify_t1(); SET SESSION binlog_format = MIXED; --echo # Check if the statement is logged in row format. let $binlog_start= query_get_value(SHOW MASTER STATUS, Position, 1); INSERT INTO t2 SET a = func_modify_t1(); --let $mask_binlog_commit_events= 1 --source include/show_binlog_events.inc --let $mask_binlog_commit_events= 0 # clean up DROP TABLE t1,t2; DROP FUNCTION func_modify_t1; # # Test case2: stmt that have more than one different tables # to update with autoinc columns should produce # unsafe warning when invoking a trigger SET SESSION binlog_format = STATEMENT; CREATE TABLE t1 (a INT); CREATE TABLE t2 (a INT, b INT PRIMARY KEY AUTO_INCREMENT); CREATE TABLE t3 (a INT, b INT PRIMARY KEY AUTO_INCREMENT); # The purpose of this function is to insert into t1 so that the second # column is auto_increment'ed. delimiter |; create trigger tri_modify_two_tables before insert on t1 for each row begin insert into t2(a) values(new.a); insert into t3(a) values(new.a); end | delimiter ;| --echo # The following statement causes auto-incrementation --echo # of both t2 and t3. It is logged in statement format, --echo # so it should produce unsafe warning INSERT INTO t1 SET a = 1; SET SESSION binlog_format = MIXED; --echo # Check if the statement is logged in row format. let $binlog_start= query_get_value(SHOW MASTER STATUS, Position, 1); INSERT INTO t1 SET a = 2; --let $mask_binlog_commit_events= 1 --source include/show_binlog_events.inc --let $mask_binlog_commit_events= 0 # clean up DROP TABLE t1,t2,t3; # # BUG#47995: Mark user functions as unsafe # BUG#49222: Mare RAND() unsafe # # Test that the system functions that are supposed to be marked unsafe # generate a warning. Each INSERT statement below should generate a # warning. # SET SESSION binlog_format = STATEMENT; CREATE TABLE t1 (a VARCHAR(1000)); INSERT INTO t1 VALUES (CURRENT_USER()); #marked unsafe before BUG#47995 INSERT INTO t1 VALUES (FOUND_ROWS()); #marked unsafe before BUG#47995 INSERT INTO t1 VALUES (GET_LOCK('tmp', 1)); #marked unsafe in BUG#47995 INSERT INTO t1 VALUES (IS_FREE_LOCK('tmp')); #marked unsafe in BUG#47995 INSERT INTO t1 VALUES (IS_USED_LOCK('tmp')); #marked unsafe in BUG#47995 INSERT INTO t1 VALUES (LOAD_FILE('../../std_data/words2.dat')); #marked unsafe in BUG#39701 INSERT INTO t1 VALUES (MASTER_POS_WAIT('dummy arg', 4711, 1)); INSERT INTO t1 VALUES (RELEASE_LOCK('tmp')); #marked unsafe in BUG#47995 INSERT INTO t1 VALUES (ROW_COUNT()); #marked unsafe before BUG#47995 INSERT INTO t1 VALUES (SESSION_USER()); #marked unsafe before BUG#47995 INSERT INTO t1 VALUES (SLEEP(1)); #marked unsafe in BUG#47995 INSERT INTO t1 VALUES (SYSDATE()); #marked unsafe in BUG#47995 INSERT INTO t1 VALUES (SYSTEM_USER()); #marked unsafe before BUG#47995 INSERT INTO t1 VALUES (USER()); #marked unsafe before BUG#47995 INSERT INTO t1 VALUES (UUID()); #marked unsafe before BUG#47995 INSERT INTO t1 VALUES (UUID_SHORT()); #marked unsafe before BUG#47995 INSERT INTO t1 VALUES (VERSION()); #marked unsafe in BUG#47995 INSERT INTO t1 VALUES (RAND()); #marked unsafe in BUG#49222 INSERT INTO t1 VALUES (RANDOM_BYTES(16)); #marked unsafe in BUG#18221667 INSERT INTO t1 VALUES (AES_ENCRYPT('a', 'a')); #marked unsafe in BUG#18221667 INSERT INTO t1 VALUES (AES_DECRYPT('a', 'a')); #marked unsafe in BUG#18221667 DELETE FROM t1; # Since we replicate the TIMESTAMP variable, functions affected by the # TIMESTAMP variable are safe to replicate. So we check that the # following following functions that depend on the TIMESTAMP variable # are not unsafe and don't generate a warning. SET TIMESTAMP=1000000; INSERT INTO t1 VALUES (CURDATE()), (CURRENT_DATE()), (CURRENT_TIME()), (CURRENT_TIMESTAMP()), (CURTIME()), (LOCALTIME()), (LOCALTIMESTAMP()), (NOW()), (UNIX_TIMESTAMP()), (UTC_DATE()), (UTC_TIME()), (UTC_TIMESTAMP()); SELECT * FROM t1; DROP TABLE t1; # #BUG#11758262-50439: MARK INSERT...SEL...ON DUP KEY UPD,REPLACE.. #The following statement may be unsafe when logged in statement format. #INSERT IGNORE...SELECT #INSERT ... SELECT ... ON DUPLICATE KEY UPDATE #REPLACE ... SELECT #UPDATE IGNORE #CREATE TABLE... IGNORE SELECT #CREATE TABLE... REPLACE SELECT # ###BUG 11765650 - 58637: MARK UPDATES THAT DEPEND ON ORDER OF TWO KEYS UNSAFE #INSERT.... ON DUP KEY UPDATE on a table with more than one UNIQUE KEY #setup tables CREATE TABLE filler_table (a INT, b INT); INSERT INTO filler_table values (1,1),(1,2); CREATE TABLE insert_table (a INT, b INT, PRIMARY KEY(a)); CREATE TABLE replace_table (a INT, b INT, PRIMARY KEY(a)); INSERT INTO replace_table values (1,1),(2,2); CREATE TABLE update_table (a INT, b INT, PRIMARY KEY(a)); INSERT INTO update_table values (1,1),(2,2); CREATE TABLE insert_2_keys (a INT UNIQUE KEY, b INT UNIQUE KEY) ENGINE = InnoDB; INSERT INTO insert_2_keys values (1, 1); #INSERT IGNORE... SELECT INSERT IGNORE INTO insert_table SELECT * FROM filler_table; TRUNCATE TABLE insert_table; #INSERT ... SELECT ... ON DUPLICATE KEY UPDATE INSERT INTO insert_table SELECT * FROM filler_table ON DUPLICATE KEY UPDATE a = 1; TRUNCATE TABLE insert_table; #REPLACE...SELECT REPLACE INTO replace_table SELECT * FROM filler_table; #UPDATE IGNORE UPDATE IGNORE update_table SET a=2; #CREATE TABLE [IGNORE/REPLACE] SELECT CREATE TABLE create_ignore_test (a INT, b INT, PRIMARY KEY(b)) IGNORE SELECT * FROM filler_table; CREATE TABLE create_replace_test (a INT, b INT, PRIMARY KEY(b)) REPLACE SELECT * FROM filler_table; #temporary tables should not throw the warning. CREATE TEMPORARY TABLE temp1 (a INT, b INT, PRIMARY KEY(b)) REPLACE SELECT * FROM filler_table; #INSERT.... ON DUP KEY UPDATE on a table with more than one UNIQUE KEY INSERT INTO insert_2_keys VALUES (1, 2) ON DUPLICATE KEY UPDATE a=VALUES(a)+10, b=VALUES(b)+10; #WAIT_FOR_EXECUTED_GTID_SET is also unsafe statement. The test for that is #added here binlog.binlog_wait_for_executed_gtid_set_unsafe_statement. ###clean up DROP TABLE filler_table; DROP TABLE insert_table; DROP TABLE update_table; DROP TABLE replace_table; DROP TABLE create_ignore_test; DROP TABLE create_replace_test; DROP TABLE insert_2_keys; --echo "End of tests"
Close
