2003-09-24 21:25:58 +02:00
|
|
|
|
# We are using .opt file since we need small binlog size
|
2005-12-22 06:39:02 +01:00
|
|
|
|
# TODO: Need to look at making a row based version once the new row based client is completed. [jbm]
|
2010-08-03 12:27:45 +02:00
|
|
|
|
-- source include/have_binlog_format_statement.inc
|
2003-09-24 21:25:58 +02:00
|
|
|
|
|
2007-06-07 19:18:01 +02:00
|
|
|
|
-- source include/have_log_bin.inc
|
2011-01-10 14:53:09 +01:00
|
|
|
|
-- source include/binlog_start_pos.inc
|
2005-03-30 03:17:46 +02:00
|
|
|
|
|
BUG#51894 Replication failure with SBR on DROP TEMPORARY TABLE inside a
transaction
BUG#52616 Temp table prevents switch binlog format from STATEMENT to ROW
Before the WL#2687 and BUG#46364, every non-transactional change that happened
after a transactional change was written to trx-cache and flushed upon
committing the transaction. WL#2687 and BUG#46364 changed this behavior and
non-transactional changes are now written to the binary log upon committing
the statement.
A binary log event is identified as transactional or non-transactional through
a flag in the Log_event which is set taking into account the underlie storage
engine on what it is stems from. In the current bug, this flag was not being
set properly when the DROP TEMPORARY TABLE was executed.
However, while fixing this bug we figured out that changes to temporary tables
should be always written to the trx-cache if there is an on-going transaction.
Otherwise, binlog events in the reversed order would be produced.
Regarding concurrency, keeping changes to temporary tables in the trx-cache is
also safe as temporary tables are only visible to the owner connection.
In this patch, we classify the following statements as unsafe:
1 - INSERT INTO t_myisam SELECT * FROM t_myisam_temp
2 - INSERT INTO t_myisam_temp SELECT * FROM t_myisam
3 - CREATE TEMPORARY TABLE t_myisam_temp SELECT * FROM t_myisam
On the other hand, the following statements are classified as safe:
1 - INSERT INTO t_innodb SELECT * FROM t_myisam_temp
2 - INSERT INTO t_myisam_temp SELECT * FROM t_innodb
The patch also guarantees that transactions that have a DROP TEMPORARY are
always written to the binary log regardless of the mode and the outcome:
commit or rollback. In particular, the DROP TEMPORARY is extended with the
IF EXISTS clause when the current statement logging format is set to row.
Finally, the patch allows to switch from STATEMENT to MIXED/ROW when there
are temporary tables but the contrary is not possible.
mysql-test/extra/rpl_tests/rpl_binlog_max_cache_size.test:
Updated the test case because
CREATE TEMPORARY TABLE t_innodb_temp SELECT * FROM t_myisam is not unsafe.
mysql-test/extra/rpl_tests/rpl_implicit_commit_binlog.test:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/extra/rpl_tests/rpl_innodb.test:
Removed comments from the test case that became false after the patch.
mysql-test/extra/rpl_tests/rpl_loaddata.test:
Suppressed warning messages due to the following cases:
1 - INSERT INTO t_myisam SELECT * FROM t_myisam_temp
2 - INSERT INTO t_myisam_temp SELECT * FROM t_myisam
mysql-test/include/ctype_utf8_table.inc:
Suppressed warning messages due to the following cases:
1 - INSERT INTO t_myisam SELECT * FROM t_myisam_temp
2 - INSERT INTO t_myisam_temp SELECT * FROM t_myisam
mysql-test/r/ctype_cp932_binlog_stm.result:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/suite/binlog/r/binlog_database.result:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/suite/binlog/r/binlog_innodb_row.result:
Updated the result file.
mysql-test/suite/binlog/r/binlog_multi_engine.result:
Updated the unsafe message.
mysql-test/suite/binlog/r/binlog_row_binlog.result:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/suite/binlog/r/binlog_row_drop_tmp_tbl.result:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/suite/binlog/r/binlog_row_mix_innodb_myisam.result:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/suite/binlog/r/binlog_stm_binlog.result:
Updated the result file.
mysql-test/suite/binlog/r/binlog_stm_mix_innodb_myisam.result:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/suite/binlog/t/binlog_tmp_table.test:
Suppressed warning messages due to the following cases:
1 - INSERT INTO t_myisam SELECT * FROM t_myisam_temp
2 - INSERT INTO t_myisam_temp SELECT * FROM t_myisam
mysql-test/suite/ndb/r/ndb_binlog_format.result:
Updated the unsafe message.
mysql-test/suite/rpl/r/rpl_concurrency_error.result:
Updated the unsafe message.
mysql-test/suite/rpl/r/rpl_mixed_binlog_max_cache_size.result:
Updated the result file because
CREATE TEMPORARY TABLE t_innodb_temp SELECT * FROM t_myisam is not unsafe.
mysql-test/suite/rpl/r/rpl_mixed_implicit_commit_binlog.result:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/suite/rpl/r/rpl_mixed_mixing_engines.result:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/suite/rpl/r/rpl_mixed_row_innodb.result:
Added some comments to ease the understanding of the result file.
mysql-test/suite/rpl/r/rpl_non_direct_mixed_mixing_engines.result:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/suite/rpl/r/rpl_non_direct_row_mixing_engines.result:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/suite/rpl/r/rpl_non_direct_stm_mixing_engines.result:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/suite/rpl/r/rpl_row_drop.result:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/suite/rpl/r/rpl_row_implicit_commit_binlog.result:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/suite/rpl/r/rpl_row_mixing_engines.result:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/suite/rpl/r/rpl_stm_binlog_max_cache_size.result:
Updated the result file because
CREATE TEMPORARY TABLE t_innodb_temp SELECT * FROM t_myisam is not unsafe.
mysql-test/suite/rpl/r/rpl_stm_implicit_commit_binlog.result:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/suite/rpl/r/rpl_stm_innodb.result:
Added some comments to ease the understanding of the result file.
mysql-test/suite/rpl/r/rpl_stm_mixing_engines.result:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/suite/rpl/r/rpl_stm_stop_middle_group.result:
Updated the unsafe message.
mysql-test/suite/rpl/r/rpl_temp_temporary.result:
Added a test case.
mysql-test/suite/rpl/t/rpl000013.test:
Suppressed warning messages due to the following cases:
1 - INSERT INTO t_myisam SELECT * FROM t_myisam_temp
2 - INSERT INTO t_myisam_temp SELECT * FROM t_myisam
3 - CREATE TEMPORARY TABLE t_myisam_temp SELECT * FROM t_myisam
mysql-test/suite/rpl/t/rpl_misc_functions.test:
Suppressed warning messages.
mysql-test/suite/rpl/t/rpl_temp_table.test:
Suppressed warning messages due to the following cases:
1 - INSERT INTO t_myisam SELECT * FROM t_myisam_temp
2 - INSERT INTO t_myisam_temp SELECT * FROM t_myisam
3 - CREATE TEMPORARY TABLE t_myisam_temp SELECT * FROM t_myisam
mysql-test/suite/rpl/t/rpl_temp_temporary.test:
Added a test case.
mysql-test/suite/rpl/t/rpl_temporary.test:
Suppressed warning messages due to the following cases:
1 - INSERT INTO t_myisam SELECT * FROM t_myisam_temp
2 - INSERT INTO t_myisam_temp SELECT * FROM t_myisam
3 - CREATE TEMPORARY TABLE t_myisam_temp SELECT * FROM t_myisam
mysql-test/suite/rpl_ndb/r/rpl_ndb_row_implicit_commit_binlog.result:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/suite/rpl_ndb/r/rpl_truncate_7ndb.result:
Updated the test case to remove references to positions
in the binary log.
mysql-test/suite/rpl_ndb/t/rpl_truncate_7ndb.test:
Updated the test case to remove references to positions
in the binary log.
mysql-test/t/create_select_tmp.test:
Suppressed warning messages due to the following cases:
1 - INSERT INTO t_myisam SELECT * FROM t_myisam_temp
2 - INSERT INTO t_myisam_temp SELECT * FROM t_myisam
3 - CREATE TEMPORARY TABLE t_myisam_temp SELECT * FROM t_myisam
mysql-test/t/ctype_cp932_binlog_stm.test:
Suppressed warning messages due to the following cases:
1 - INSERT INTO t_myisam SELECT * FROM t_myisam_temp
2 - INSERT INTO t_myisam_temp SELECT * FROM t_myisam
3 - CREATE TEMPORARY TABLE t_myisam_temp SELECT * FROM t_myisam
mysql-test/t/mysqlbinlog.test:
Suppressed warning messages due to the following cases:
1 - INSERT INTO t_myisam SELECT * FROM t_myisam_temp
2 - INSERT INTO t_myisam_temp SELECT * FROM t_myisam
3 - CREATE TEMPORARY TABLE t_myisam_temp SELECT * FROM t_myisam
sql/log.cc:
Improved the code by creating several functions to hide decision
on type of engine changed, commit/abort, etc:
. stmt_has_updated_non_trans_table
. trans_has_updated_non_trans_table
. ending_trans
Updated the binlog_rollback function and the use of the
OPTION_KEEP_LOG which indincates when a temporary table was
either created or dropped and as such the command must be
logged if not in MIXED mode and even while rolling back the
transaction.
sql/log.h:
Improved the code by creating several functions to hide decision
on type of engine changed, commit/abort, etc.
sql/log_event.cc:
Removed the setting of the OPTION_KEEP_LOG as it is related to CREATE
TEMPORARY and DROP TEMPORARY and not to the type of engine (i.e.
transactional or non-transactional).
sql/log_event_old.cc:
Removed the setting of the OPTION_KEEP_LOG as it is related to CREATE
TEMPORARY and DROP TEMPORARY and not to the type of engine (i.e.
transactional or non-transactional).
sql/share/errmsg-utf8.txt:
Updated the unsafe message.
sql/sql_class.cc:
Classifies the following statements as unsafe:
1 - INSERT INTO t_myisam SELECT * FROM t_myisam_temp
2 - INSERT INTO t_myisam_temp SELECT * FROM t_myisam
On the other hand, the following statements are classified as safe:
1 - INSERT INTO t_innodb SELECT * FROM t_myisam_temp
2 - INSERT INTO t_myisam_temp SELECT * FROM t_innodb
sql/sql_class.h:
It allows to switch from STATEMENT to MIXED/ROW when there are temporary
tables but the contrary is not possible.
sql/sql_table.cc:
Fixed the case that a DROP/DROP TEMPORARY that affects a temporary table in MIXED
mode is written as a DROP TEMPORARY TABLE IF EXISTS because the table may not exist in the slave and due to the IF EXISTS token an error will never happen
while processing the statement in the slave.
Removed a function that was not being used.
2010-04-20 11:10:43 +02:00
|
|
|
|
--disable_query_log
|
2010-04-28 14:47:49 +02:00
|
|
|
|
CALL mtr.add_suppression("Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT");
|
BUG#51894 Replication failure with SBR on DROP TEMPORARY TABLE inside a
transaction
BUG#52616 Temp table prevents switch binlog format from STATEMENT to ROW
Before the WL#2687 and BUG#46364, every non-transactional change that happened
after a transactional change was written to trx-cache and flushed upon
committing the transaction. WL#2687 and BUG#46364 changed this behavior and
non-transactional changes are now written to the binary log upon committing
the statement.
A binary log event is identified as transactional or non-transactional through
a flag in the Log_event which is set taking into account the underlie storage
engine on what it is stems from. In the current bug, this flag was not being
set properly when the DROP TEMPORARY TABLE was executed.
However, while fixing this bug we figured out that changes to temporary tables
should be always written to the trx-cache if there is an on-going transaction.
Otherwise, binlog events in the reversed order would be produced.
Regarding concurrency, keeping changes to temporary tables in the trx-cache is
also safe as temporary tables are only visible to the owner connection.
In this patch, we classify the following statements as unsafe:
1 - INSERT INTO t_myisam SELECT * FROM t_myisam_temp
2 - INSERT INTO t_myisam_temp SELECT * FROM t_myisam
3 - CREATE TEMPORARY TABLE t_myisam_temp SELECT * FROM t_myisam
On the other hand, the following statements are classified as safe:
1 - INSERT INTO t_innodb SELECT * FROM t_myisam_temp
2 - INSERT INTO t_myisam_temp SELECT * FROM t_innodb
The patch also guarantees that transactions that have a DROP TEMPORARY are
always written to the binary log regardless of the mode and the outcome:
commit or rollback. In particular, the DROP TEMPORARY is extended with the
IF EXISTS clause when the current statement logging format is set to row.
Finally, the patch allows to switch from STATEMENT to MIXED/ROW when there
are temporary tables but the contrary is not possible.
mysql-test/extra/rpl_tests/rpl_binlog_max_cache_size.test:
Updated the test case because
CREATE TEMPORARY TABLE t_innodb_temp SELECT * FROM t_myisam is not unsafe.
mysql-test/extra/rpl_tests/rpl_implicit_commit_binlog.test:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/extra/rpl_tests/rpl_innodb.test:
Removed comments from the test case that became false after the patch.
mysql-test/extra/rpl_tests/rpl_loaddata.test:
Suppressed warning messages due to the following cases:
1 - INSERT INTO t_myisam SELECT * FROM t_myisam_temp
2 - INSERT INTO t_myisam_temp SELECT * FROM t_myisam
mysql-test/include/ctype_utf8_table.inc:
Suppressed warning messages due to the following cases:
1 - INSERT INTO t_myisam SELECT * FROM t_myisam_temp
2 - INSERT INTO t_myisam_temp SELECT * FROM t_myisam
mysql-test/r/ctype_cp932_binlog_stm.result:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/suite/binlog/r/binlog_database.result:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/suite/binlog/r/binlog_innodb_row.result:
Updated the result file.
mysql-test/suite/binlog/r/binlog_multi_engine.result:
Updated the unsafe message.
mysql-test/suite/binlog/r/binlog_row_binlog.result:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/suite/binlog/r/binlog_row_drop_tmp_tbl.result:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/suite/binlog/r/binlog_row_mix_innodb_myisam.result:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/suite/binlog/r/binlog_stm_binlog.result:
Updated the result file.
mysql-test/suite/binlog/r/binlog_stm_mix_innodb_myisam.result:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/suite/binlog/t/binlog_tmp_table.test:
Suppressed warning messages due to the following cases:
1 - INSERT INTO t_myisam SELECT * FROM t_myisam_temp
2 - INSERT INTO t_myisam_temp SELECT * FROM t_myisam
mysql-test/suite/ndb/r/ndb_binlog_format.result:
Updated the unsafe message.
mysql-test/suite/rpl/r/rpl_concurrency_error.result:
Updated the unsafe message.
mysql-test/suite/rpl/r/rpl_mixed_binlog_max_cache_size.result:
Updated the result file because
CREATE TEMPORARY TABLE t_innodb_temp SELECT * FROM t_myisam is not unsafe.
mysql-test/suite/rpl/r/rpl_mixed_implicit_commit_binlog.result:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/suite/rpl/r/rpl_mixed_mixing_engines.result:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/suite/rpl/r/rpl_mixed_row_innodb.result:
Added some comments to ease the understanding of the result file.
mysql-test/suite/rpl/r/rpl_non_direct_mixed_mixing_engines.result:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/suite/rpl/r/rpl_non_direct_row_mixing_engines.result:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/suite/rpl/r/rpl_non_direct_stm_mixing_engines.result:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/suite/rpl/r/rpl_row_drop.result:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/suite/rpl/r/rpl_row_implicit_commit_binlog.result:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/suite/rpl/r/rpl_row_mixing_engines.result:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/suite/rpl/r/rpl_stm_binlog_max_cache_size.result:
Updated the result file because
CREATE TEMPORARY TABLE t_innodb_temp SELECT * FROM t_myisam is not unsafe.
mysql-test/suite/rpl/r/rpl_stm_implicit_commit_binlog.result:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/suite/rpl/r/rpl_stm_innodb.result:
Added some comments to ease the understanding of the result file.
mysql-test/suite/rpl/r/rpl_stm_mixing_engines.result:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/suite/rpl/r/rpl_stm_stop_middle_group.result:
Updated the unsafe message.
mysql-test/suite/rpl/r/rpl_temp_temporary.result:
Added a test case.
mysql-test/suite/rpl/t/rpl000013.test:
Suppressed warning messages due to the following cases:
1 - INSERT INTO t_myisam SELECT * FROM t_myisam_temp
2 - INSERT INTO t_myisam_temp SELECT * FROM t_myisam
3 - CREATE TEMPORARY TABLE t_myisam_temp SELECT * FROM t_myisam
mysql-test/suite/rpl/t/rpl_misc_functions.test:
Suppressed warning messages.
mysql-test/suite/rpl/t/rpl_temp_table.test:
Suppressed warning messages due to the following cases:
1 - INSERT INTO t_myisam SELECT * FROM t_myisam_temp
2 - INSERT INTO t_myisam_temp SELECT * FROM t_myisam
3 - CREATE TEMPORARY TABLE t_myisam_temp SELECT * FROM t_myisam
mysql-test/suite/rpl/t/rpl_temp_temporary.test:
Added a test case.
mysql-test/suite/rpl/t/rpl_temporary.test:
Suppressed warning messages due to the following cases:
1 - INSERT INTO t_myisam SELECT * FROM t_myisam_temp
2 - INSERT INTO t_myisam_temp SELECT * FROM t_myisam
3 - CREATE TEMPORARY TABLE t_myisam_temp SELECT * FROM t_myisam
mysql-test/suite/rpl_ndb/r/rpl_ndb_row_implicit_commit_binlog.result:
Updated the test case due to the new rules: changes to
temporary tables are written to the binary log in the
boundaries of a transaction if there is any.
mysql-test/suite/rpl_ndb/r/rpl_truncate_7ndb.result:
Updated the test case to remove references to positions
in the binary log.
mysql-test/suite/rpl_ndb/t/rpl_truncate_7ndb.test:
Updated the test case to remove references to positions
in the binary log.
mysql-test/t/create_select_tmp.test:
Suppressed warning messages due to the following cases:
1 - INSERT INTO t_myisam SELECT * FROM t_myisam_temp
2 - INSERT INTO t_myisam_temp SELECT * FROM t_myisam
3 - CREATE TEMPORARY TABLE t_myisam_temp SELECT * FROM t_myisam
mysql-test/t/ctype_cp932_binlog_stm.test:
Suppressed warning messages due to the following cases:
1 - INSERT INTO t_myisam SELECT * FROM t_myisam_temp
2 - INSERT INTO t_myisam_temp SELECT * FROM t_myisam
3 - CREATE TEMPORARY TABLE t_myisam_temp SELECT * FROM t_myisam
mysql-test/t/mysqlbinlog.test:
Suppressed warning messages due to the following cases:
1 - INSERT INTO t_myisam SELECT * FROM t_myisam_temp
2 - INSERT INTO t_myisam_temp SELECT * FROM t_myisam
3 - CREATE TEMPORARY TABLE t_myisam_temp SELECT * FROM t_myisam
sql/log.cc:
Improved the code by creating several functions to hide decision
on type of engine changed, commit/abort, etc:
. stmt_has_updated_non_trans_table
. trans_has_updated_non_trans_table
. ending_trans
Updated the binlog_rollback function and the use of the
OPTION_KEEP_LOG which indincates when a temporary table was
either created or dropped and as such the command must be
logged if not in MIXED mode and even while rolling back the
transaction.
sql/log.h:
Improved the code by creating several functions to hide decision
on type of engine changed, commit/abort, etc.
sql/log_event.cc:
Removed the setting of the OPTION_KEEP_LOG as it is related to CREATE
TEMPORARY and DROP TEMPORARY and not to the type of engine (i.e.
transactional or non-transactional).
sql/log_event_old.cc:
Removed the setting of the OPTION_KEEP_LOG as it is related to CREATE
TEMPORARY and DROP TEMPORARY and not to the type of engine (i.e.
transactional or non-transactional).
sql/share/errmsg-utf8.txt:
Updated the unsafe message.
sql/sql_class.cc:
Classifies the following statements as unsafe:
1 - INSERT INTO t_myisam SELECT * FROM t_myisam_temp
2 - INSERT INTO t_myisam_temp SELECT * FROM t_myisam
On the other hand, the following statements are classified as safe:
1 - INSERT INTO t_innodb SELECT * FROM t_myisam_temp
2 - INSERT INTO t_myisam_temp SELECT * FROM t_innodb
sql/sql_class.h:
It allows to switch from STATEMENT to MIXED/ROW when there are temporary
tables but the contrary is not possible.
sql/sql_table.cc:
Fixed the case that a DROP/DROP TEMPORARY that affects a temporary table in MIXED
mode is written as a DROP TEMPORARY TABLE IF EXISTS because the table may not exist in the slave and due to the IF EXISTS token an error will never happen
while processing the statement in the slave.
Removed a function that was not being used.
2010-04-20 11:10:43 +02:00
|
|
|
|
--enable_query_log
|
|
|
|
|
|
|
2008-01-08 21:45:15 +01:00
|
|
|
|
# Deletes all the binary logs
|
|
|
|
|
|
reset master;
|
|
|
|
|
|
|
2003-09-24 21:25:58 +02:00
|
|
|
|
# we need this for getting fixed timestamps inside of this test
|
|
|
|
|
|
set timestamp=1000000000;
|
|
|
|
|
|
|
2004-06-09 16:07:01 +02:00
|
|
|
|
--disable_warnings
|
2007-01-22 14:52:15 +01:00
|
|
|
|
drop table if exists t1,t2,t3,t4,t5,t03,t04;
|
2004-06-09 16:07:01 +02:00
|
|
|
|
--enable_warnings
|
|
|
|
|
|
|
2003-09-24 21:25:58 +02:00
|
|
|
|
create table t1 (word varchar(20));
|
|
|
|
|
|
create table t2 (id int auto_increment not null primary key);
|
|
|
|
|
|
|
|
|
|
|
|
# simple test for simple statement and various events
|
|
|
|
|
|
insert into t1 values ("abirvalg");
|
|
|
|
|
|
insert into t2 values ();
|
|
|
|
|
|
# Should be uncommented in 4.1
|
|
|
|
|
|
# set @a:=1
|
|
|
|
|
|
# insert into t2 values (@a);
|
|
|
|
|
|
|
2009-03-03 21:34:18 +01:00
|
|
|
|
# test for load data and load data distributed among the several
|
2003-09-24 21:25:58 +02:00
|
|
|
|
# files (we need to fill up first binlog)
|
2011-01-10 14:53:09 +01:00
|
|
|
|
load data infile '../../std_data/words3.dat' into table t1;
|
|
|
|
|
|
load data infile '../../std_data/words3.dat' into table t1;
|
|
|
|
|
|
load data infile '../../std_data/words3.dat' into table t1;
|
|
|
|
|
|
load data infile '../../std_data/words3.dat' into table t1;
|
|
|
|
|
|
load data infile '../../std_data/words3.dat' into table t1;
|
2003-09-24 21:25:58 +02:00
|
|
|
|
# simple query to show more in second binlog
|
2010-07-16 20:25:00 +02:00
|
|
|
|
--let $binlog_start_pos=query_get_value(SHOW MASTER STATUS, Position, 1)
|
2003-09-24 21:25:58 +02:00
|
|
|
|
insert into t1 values ("Alas");
|
2011-01-10 14:53:09 +01:00
|
|
|
|
|
|
|
|
|
|
### Starting master-bin.000003
|
2003-09-24 21:25:58 +02:00
|
|
|
|
flush logs;
|
|
|
|
|
|
|
|
|
|
|
|
# delimiters are for easier debugging in future
|
|
|
|
|
|
--disable_query_log
|
|
|
|
|
|
select "--- Local --" as "";
|
|
|
|
|
|
--enable_query_log
|
|
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
|
# We should use --short-form everywhere because in other case output will
|
|
|
|
|
|
# be time dependend. Better than nothing.
|
|
|
|
|
|
#
|
2007-12-12 18:19:24 +01:00
|
|
|
|
let $MYSQLD_DATADIR= `select @@datadir`;
|
2006-01-24 08:30:54 +01:00
|
|
|
|
--replace_result $MYSQLTEST_VARDIR MYSQLTEST_VARDIR
|
2019-08-30 15:06:54 +02:00
|
|
|
|
--replace_regex /SQL_LOAD_MB-[0-9a-f]+-[0-9a-f]+/SQL_LOAD_MB-#-#/ /@@session.sql_mode=\d+/@@session.sql_mode=#/ /collation_server=\d+/collation_server=#/
|
2007-12-12 18:19:24 +01:00
|
|
|
|
--exec $MYSQL_BINLOG --short-form --local-load=$MYSQLTEST_VARDIR/tmp/ $MYSQLD_DATADIR/master-bin.000001
|
2003-09-29 21:10:30 +02:00
|
|
|
|
|
2003-09-24 21:25:58 +02:00
|
|
|
|
# this should not fail but shouldn't produce any working statements
|
|
|
|
|
|
--disable_query_log
|
|
|
|
|
|
select "--- Broken LOAD DATA --" as "";
|
|
|
|
|
|
--enable_query_log
|
2006-01-24 08:30:54 +01:00
|
|
|
|
--replace_result $MYSQLTEST_VARDIR MYSQLTEST_VARDIR
|
2019-08-30 15:06:54 +02:00
|
|
|
|
--replace_regex /SQL_LOAD_MB-[0-9a-f]+-[0-9a-f]+/SQL_LOAD_MB-#-#/ /@@session.sql_mode=\d+/@@session.sql_mode=#/ /collation_server=\d+/collation_server=#/
|
2007-12-12 18:19:24 +01:00
|
|
|
|
--exec $MYSQL_BINLOG --short-form --local-load=$MYSQLTEST_VARDIR/tmp/ $MYSQLD_DATADIR/master-bin.000002 2> /dev/null
|
2003-09-24 21:25:58 +02:00
|
|
|
|
|
|
|
|
|
|
# this should show almost nothing
|
|
|
|
|
|
--disable_query_log
|
|
|
|
|
|
select "--- --database --" as "";
|
|
|
|
|
|
--enable_query_log
|
2006-01-24 08:30:54 +01:00
|
|
|
|
--replace_result $MYSQLTEST_VARDIR MYSQLTEST_VARDIR
|
2019-08-30 15:06:54 +02:00
|
|
|
|
--replace_regex /SQL_LOAD_MB-[0-9a-f]+-[0-9a-f]+/SQL_LOAD_MB-#-#/ /@@session.sql_mode=\d+/@@session.sql_mode=#/ /collation_server=\d+/collation_server=#/
|
2007-12-12 18:19:24 +01:00
|
|
|
|
--exec $MYSQL_BINLOG --short-form --local-load=$MYSQLTEST_VARDIR/tmp/ --database=nottest $MYSQLD_DATADIR/master-bin.000001 2> /dev/null
|
2003-09-24 21:25:58 +02:00
|
|
|
|
|
2010-02-17 10:18:17 +01:00
|
|
|
|
# this test for start-position option
|
2003-09-24 21:25:58 +02:00
|
|
|
|
--disable_query_log
|
2010-02-17 10:18:17 +01:00
|
|
|
|
select "--- --start-position --" as "";
|
2003-09-24 21:25:58 +02:00
|
|
|
|
--enable_query_log
|
2006-01-24 08:30:54 +01:00
|
|
|
|
--replace_result $MYSQLTEST_VARDIR MYSQLTEST_VARDIR
|
2019-08-30 15:06:54 +02:00
|
|
|
|
--replace_regex /SQL_LOAD_MB-[0-9a-f]+-[0-9a-f]+/SQL_LOAD_MB-#-#/ /@@session.sql_mode=\d+/@@session.sql_mode=#/ /collation_server=\d+/collation_server=#/
|
2010-07-16 20:25:00 +02:00
|
|
|
|
--exec $MYSQL_BINLOG --short-form --local-load=$MYSQLTEST_VARDIR/tmp/ --start-position=$binlog_start_pos $MYSQLD_DATADIR/master-bin.000002
|
2003-09-24 21:25:58 +02:00
|
|
|
|
|
|
|
|
|
|
# These are tests for remote binlog.
|
|
|
|
|
|
# They should return the same as previous test.
|
|
|
|
|
|
|
|
|
|
|
|
--disable_query_log
|
|
|
|
|
|
select "--- Remote --" as "";
|
|
|
|
|
|
--enable_query_log
|
|
|
|
|
|
|
|
|
|
|
|
# This is broken now
|
2006-01-24 08:30:54 +01:00
|
|
|
|
--replace_result $MYSQLTEST_VARDIR MYSQLTEST_VARDIR
|
2019-08-30 15:06:54 +02:00
|
|
|
|
--replace_regex /SQL_LOAD_MB-[0-9a-f]+-[0-9a-f]+/SQL_LOAD_MB-#-#/ /@@session.sql_mode=\d+/@@session.sql_mode=#/ /collation_server=\d+/collation_server=#/
|
2006-01-24 08:30:54 +01:00
|
|
|
|
--exec $MYSQL_BINLOG --short-form --local-load=$MYSQLTEST_VARDIR/tmp/ --read-from-remote-server --user=root --host=127.0.0.1 --port=$MASTER_MYPORT master-bin.000001
|
2003-09-24 21:25:58 +02:00
|
|
|
|
|
|
|
|
|
|
# This is broken too
|
|
|
|
|
|
--disable_query_log
|
|
|
|
|
|
select "--- Broken LOAD DATA --" as "";
|
|
|
|
|
|
--enable_query_log
|
2006-01-24 08:30:54 +01:00
|
|
|
|
--replace_result $MYSQLTEST_VARDIR MYSQLTEST_VARDIR
|
2019-08-30 15:06:54 +02:00
|
|
|
|
--replace_regex /SQL_LOAD_MB-[0-9a-f]+-[0-9a-f]+/SQL_LOAD_MB-#-#/ /@@session.sql_mode=\d+/@@session.sql_mode=#/ /collation_server=\d+/collation_server=#/
|
2006-07-29 11:43:34 +02:00
|
|
|
|
--exec $MYSQL_BINLOG --short-form --local-load=$MYSQLTEST_VARDIR/tmp/ --read-from-remote-server --user=root --host=127.0.0.1 --port=$MASTER_MYPORT master-bin.000002 2> /dev/null
|
2003-09-24 21:25:58 +02:00
|
|
|
|
|
|
|
|
|
|
# And this too ! (altough it is documented)
|
|
|
|
|
|
--disable_query_log
|
|
|
|
|
|
select "--- --database --" as "";
|
|
|
|
|
|
--enable_query_log
|
2006-01-24 08:30:54 +01:00
|
|
|
|
--replace_result $MYSQLTEST_VARDIR MYSQLTEST_VARDIR
|
2019-08-30 15:06:54 +02:00
|
|
|
|
--replace_regex /SQL_LOAD_MB-[0-9a-f]+-[0-9a-f]+/SQL_LOAD_MB-#-#/ /@@session.sql_mode=\d+/@@session.sql_mode=#/ /collation_server=\d+/collation_server=#/
|
2006-07-29 11:43:34 +02:00
|
|
|
|
--exec $MYSQL_BINLOG --short-form --local-load=$MYSQLTEST_VARDIR/tmp/ --read-from-remote-server --user=root --host=127.0.0.1 --port=$MASTER_MYPORT --database=nottest master-bin.000001 2> /dev/null
|
2003-09-24 21:25:58 +02:00
|
|
|
|
|
|
|
|
|
|
# Strangely but this works
|
|
|
|
|
|
--disable_query_log
|
2010-02-17 10:18:17 +01:00
|
|
|
|
select "--- --start-position --" as "";
|
2003-09-24 21:25:58 +02:00
|
|
|
|
--enable_query_log
|
2006-01-24 08:30:54 +01:00
|
|
|
|
--replace_result $MYSQLTEST_VARDIR MYSQLTEST_VARDIR
|
2019-08-30 15:06:54 +02:00
|
|
|
|
--replace_regex /SQL_LOAD_MB-[0-9a-f]+-[0-9a-f]+/SQL_LOAD_MB-#-#/ /@@session.sql_mode=\d+/@@session.sql_mode=#/ /collation_server=\d+/collation_server=#/
|
2010-07-16 20:25:00 +02:00
|
|
|
|
--exec $MYSQL_BINLOG --short-form --local-load=$MYSQLTEST_VARDIR/tmp/ --read-from-remote-server --start-position=$binlog_start_pos --user=root --host=127.0.0.1 --port=$MASTER_MYPORT master-bin.000002
|
2003-09-24 21:25:58 +02:00
|
|
|
|
|
2009-03-03 21:34:18 +01:00
|
|
|
|
# Bug#7853 mysqlbinlog does not accept input from stdin
|
2005-02-04 14:29:54 +01:00
|
|
|
|
--disable_query_log
|
|
|
|
|
|
select "--- reading stdin --" as "";
|
|
|
|
|
|
--enable_query_log
|
|
|
|
|
|
--replace_result $MYSQL_TEST_DIR MYSQL_TEST_DIR
|
2019-08-30 15:06:54 +02:00
|
|
|
|
--replace_regex /SQL_LOAD_MB-[0-9a-f]+-[0-9a-f]+/SQL_LOAD_MB-#-#/ /@@session.sql_mode=\d+/@@session.sql_mode=#/ /collation_server=\d+/collation_server=#/
|
2005-09-24 04:11:51 +02:00
|
|
|
|
--exec $MYSQL_BINLOG --short-form - < $MYSQL_TEST_DIR/std_data/trunc_binlog.000001
|
2005-02-04 14:29:54 +01:00
|
|
|
|
|
|
|
|
|
|
--replace_result $MYSQL_TEST_DIR MYSQL_TEST_DIR
|
2019-08-30 15:06:54 +02:00
|
|
|
|
--replace_regex /SQL_LOAD_MB-[0-9a-f]+-[0-9a-f]+/SQL_LOAD_MB-#-#/ /@@session.sql_mode=\d+/@@session.sql_mode=#/ /collation_server=\d+/collation_server=#/
|
2010-07-16 20:25:00 +02:00
|
|
|
|
# postion is constant to correspond to an event in pre-recorded binlog
|
|
|
|
|
|
--let $binlog_start_pos=79
|
|
|
|
|
|
--exec $MYSQL_BINLOG --short-form --start-position=$binlog_start_pos - < $MYSQL_TEST_DIR/std_data/trunc_binlog.000001
|
2007-01-22 14:52:15 +01:00
|
|
|
|
drop table t1,t2;
|
2005-02-04 14:29:54 +01:00
|
|
|
|
|
2006-05-09 22:01:31 +02:00
|
|
|
|
#
|
2009-03-03 21:34:18 +01:00
|
|
|
|
# Bug#14157 utf8 encoding in binlog without set character_set_client
|
2006-05-09 22:01:31 +02:00
|
|
|
|
#
|
2011-01-10 14:53:09 +01:00
|
|
|
|
### Starting master-bin.000004
|
2006-05-09 22:01:31 +02:00
|
|
|
|
flush logs;
|
2011-01-10 14:53:09 +01:00
|
|
|
|
|
2007-02-19 17:40:34 +01:00
|
|
|
|
--write_file $MYSQLTEST_VARDIR/tmp/bug14157.sql
|
|
|
|
|
|
create table if not exists t5 (a int);
|
|
|
|
|
|
set names latin1;
|
|
|
|
|
|
create temporary table `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` (a int);
|
|
|
|
|
|
insert into `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` values (1);
|
|
|
|
|
|
insert into t5 select * from `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`
|
|
|
|
|
|
EOF
|
|
|
|
|
|
--exec $MYSQL test < $MYSQLTEST_VARDIR/tmp/bug14157.sql
|
|
|
|
|
|
--remove_file $MYSQLTEST_VARDIR/tmp/bug14157.sql
|
2006-02-09 15:23:09 +01:00
|
|
|
|
|
2009-03-03 21:34:18 +01:00
|
|
|
|
# resulted binlog, parly consisting of multi-byte utf8 chars,
|
|
|
|
|
|
# must be digestable for both client and server. In 4.1 the client
|
2006-05-20 11:34:56 +02:00
|
|
|
|
# should use default-character-set same as the server.
|
2011-01-10 14:53:09 +01:00
|
|
|
|
|
|
|
|
|
|
### Starting master-bin.000005
|
2006-12-14 11:05:25 +01:00
|
|
|
|
flush logs;
|
2010-04-21 15:28:00 +02:00
|
|
|
|
# Due to BUG#18337 that wrongly suppresses the BINLOG EVENTS when
|
|
|
|
|
|
# --short-form is used, the "insert into t5 select * from `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`"
|
|
|
|
|
|
# which is unsafe and thus written to the binary log in the row
|
|
|
|
|
|
# format is not executed. This makes the assertion select * from t5
|
|
|
|
|
|
# /* must be (1),(1) */; to fail. To temporary fix the bug, we
|
|
|
|
|
|
# removed the option --short-form.
|
|
|
|
|
|
#--exec $MYSQL_BINLOG --short-form $MYSQLD_DATADIR/master-bin.000004 | $MYSQL
|
|
|
|
|
|
--exec $MYSQL_BINLOG $MYSQLD_DATADIR/master-bin.000004 | $MYSQL
|
2006-05-09 22:01:31 +02:00
|
|
|
|
select * from t5 /* must be (1),(1) */;
|
2007-01-22 14:52:15 +01:00
|
|
|
|
drop table t5;
|
2006-02-09 15:23:09 +01:00
|
|
|
|
|
2006-12-07 06:31:53 +01:00
|
|
|
|
#
|
|
|
|
|
|
# Bug#22645 LC_TIME_NAMES: Statement not replicated
|
|
|
|
|
|
# Check that a dump created by mysqlbinlog reproduces
|
|
|
|
|
|
# lc_time_names dependent values correctly
|
|
|
|
|
|
#
|
2011-01-10 14:53:09 +01:00
|
|
|
|
|
|
|
|
|
|
### Starting master-bin.000006
|
2006-12-07 06:31:53 +01:00
|
|
|
|
flush logs;
|
|
|
|
|
|
create table t5 (c1 int, c2 varchar(128) character set latin1 not null);
|
|
|
|
|
|
insert into t5 values (1, date_format('2001-01-01','%W'));
|
|
|
|
|
|
set lc_time_names=de_DE;
|
|
|
|
|
|
insert into t5 values (2, date_format('2001-01-01','%W'));
|
|
|
|
|
|
set lc_time_names=en_US;
|
|
|
|
|
|
insert into t5 values (3, date_format('2001-01-01','%W'));
|
|
|
|
|
|
select * from t5 order by c1;
|
2011-01-10 14:53:09 +01:00
|
|
|
|
|
|
|
|
|
|
### Starting master-bin.000007
|
2006-12-07 06:31:53 +01:00
|
|
|
|
flush logs;
|
2011-01-10 14:53:09 +01:00
|
|
|
|
|
2006-12-07 06:31:53 +01:00
|
|
|
|
drop table t5;
|
2007-12-12 18:19:24 +01:00
|
|
|
|
--exec $MYSQL_BINLOG --short-form $MYSQLD_DATADIR/master-bin.000006 | $MYSQL
|
2006-12-07 06:31:53 +01:00
|
|
|
|
select * from t5 order by c1;
|
2007-01-22 14:52:15 +01:00
|
|
|
|
drop table t5;
|
|
|
|
|
|
|
2006-11-28 13:26:15 +01:00
|
|
|
|
#
|
2009-03-03 21:34:18 +01:00
|
|
|
|
# Bug#20396 Bin Log does not get DELIMETER cmd - Recover StoredProc fails
|
2006-11-28 13:26:15 +01:00
|
|
|
|
#
|
|
|
|
|
|
--disable_warnings
|
|
|
|
|
|
drop procedure if exists p1;
|
|
|
|
|
|
--enable_warnings
|
2011-01-10 14:53:09 +01:00
|
|
|
|
|
|
|
|
|
|
### Starting master-bin.000008
|
2006-11-28 13:26:15 +01:00
|
|
|
|
flush logs;
|
2011-01-10 14:53:09 +01:00
|
|
|
|
|
2006-11-28 13:26:15 +01:00
|
|
|
|
delimiter //;
|
|
|
|
|
|
create procedure p1()
|
|
|
|
|
|
begin
|
|
|
|
|
|
select 1;
|
|
|
|
|
|
end;
|
|
|
|
|
|
//
|
|
|
|
|
|
delimiter ;//
|
2011-01-10 14:53:09 +01:00
|
|
|
|
|
|
|
|
|
|
### Starting master-bin.000009
|
2006-11-28 13:26:15 +01:00
|
|
|
|
flush logs;
|
2011-01-10 14:53:09 +01:00
|
|
|
|
|
2006-11-28 13:26:15 +01:00
|
|
|
|
call p1();
|
|
|
|
|
|
drop procedure p1;
|
2009-02-19 21:37:40 +01:00
|
|
|
|
--error ER_SP_DOES_NOT_EXIST
|
2006-11-28 13:26:15 +01:00
|
|
|
|
call p1();
|
2019-08-30 15:06:54 +02:00
|
|
|
|
--replace_regex /SQL_LOAD_MB-[0-9a-f]+-[0-9a-f]+/SQL_LOAD_MB-#-#/ /@@session.sql_mode=\d+/@@session.sql_mode=#/ /collation_server=\d+/collation_server=#/
|
2007-12-12 18:19:24 +01:00
|
|
|
|
--exec $MYSQL_BINLOG --short-form $MYSQLD_DATADIR/master-bin.000008
|
|
|
|
|
|
--exec $MYSQL_BINLOG --short-form $MYSQLD_DATADIR/master-bin.000008 | $MYSQL
|
2006-11-28 13:26:15 +01:00
|
|
|
|
call p1();
|
|
|
|
|
|
drop procedure p1;
|
|
|
|
|
|
|
2007-01-22 14:52:15 +01:00
|
|
|
|
#
|
2006-12-14 23:51:37 +01:00
|
|
|
|
# Some coverage of not normally used parts
|
|
|
|
|
|
#
|
|
|
|
|
|
--disable_query_log
|
|
|
|
|
|
--exec $MYSQL_BINLOG --version 2>&1 > /dev/null
|
|
|
|
|
|
--exec $MYSQL_BINLOG --help 2>&1 > /dev/null
|
|
|
|
|
|
--enable_query_log
|
2005-02-14 21:50:09 +01:00
|
|
|
|
|
2007-02-28 14:06:57 +01:00
|
|
|
|
#
|
|
|
|
|
|
# Bug#15126 character_set_database is not replicated
|
|
|
|
|
|
# (LOAD DATA INFILE need it)
|
|
|
|
|
|
#
|
|
|
|
|
|
|
2011-01-10 14:53:09 +01:00
|
|
|
|
### Starting master-bin.000010
|
2007-02-28 14:06:57 +01:00
|
|
|
|
flush logs;
|
2011-01-10 14:53:09 +01:00
|
|
|
|
|
2007-02-28 14:06:57 +01:00
|
|
|
|
create table t1 (a varchar(64) character set utf8);
|
2007-12-12 18:19:24 +01:00
|
|
|
|
load data infile '../../std_data/loaddata6.dat' into table t1;
|
2007-02-28 14:06:57 +01:00
|
|
|
|
set character_set_database=koi8r;
|
2007-12-12 18:19:24 +01:00
|
|
|
|
load data infile '../../std_data/loaddata6.dat' into table t1;
|
2007-02-28 14:06:57 +01:00
|
|
|
|
set character_set_database=latin1;
|
2007-12-12 18:19:24 +01:00
|
|
|
|
load data infile '../../std_data/loaddata6.dat' into table t1;
|
|
|
|
|
|
load data infile '../../std_data/loaddata6.dat' into table t1;
|
2007-02-28 14:06:57 +01:00
|
|
|
|
set character_set_database=koi8r;
|
2007-12-12 18:19:24 +01:00
|
|
|
|
load data infile '../../std_data/loaddata6.dat' into table t1;
|
2007-02-28 14:06:57 +01:00
|
|
|
|
set character_set_database=latin1;
|
2007-12-12 18:19:24 +01:00
|
|
|
|
load data infile '../../std_data/loaddata6.dat' into table t1;
|
|
|
|
|
|
load data infile '../../std_data/loaddata6.dat' into table t1 character set koi8r;
|
2007-02-28 14:06:57 +01:00
|
|
|
|
select hex(a) from t1;
|
|
|
|
|
|
drop table t1;
|
2011-01-10 14:53:09 +01:00
|
|
|
|
|
|
|
|
|
|
### Starting master-bin.000011
|
2007-02-28 14:06:57 +01:00
|
|
|
|
flush logs;
|
2011-01-10 14:53:09 +01:00
|
|
|
|
|
2007-03-31 17:18:03 +02:00
|
|
|
|
--replace_result $MYSQLTEST_VARDIR MYSQLTEST_VARDIR
|
2019-08-30 15:06:54 +02:00
|
|
|
|
--replace_regex /SQL_LOAD_MB-[0-9a-f]+-[0-9a-f]+/SQL_LOAD_MB-#-#/ /@@session.sql_mode=\d+/@@session.sql_mode=#/ /collation_server=\d+/collation_server=#/
|
2007-12-12 18:19:24 +01:00
|
|
|
|
--exec $MYSQL_BINLOG --short-form --local-load=$MYSQLTEST_VARDIR/tmp/ $MYSQLD_DATADIR/master-bin.000010
|
2006-11-28 13:26:15 +01:00
|
|
|
|
|
2007-06-20 23:11:28 +02:00
|
|
|
|
#
|
|
|
|
|
|
# Bug#28293 missed '#' sign in the hex dump when the dump length
|
2009-03-05 14:35:03 +01:00
|
|
|
|
# is divisible by 16.
|
2007-06-20 23:11:28 +02:00
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
|
|
CREATE TABLE t1 (c1 CHAR(10));
|
|
|
|
|
|
# we need this for getting fixed timestamps inside of this test
|
2011-01-10 14:53:09 +01:00
|
|
|
|
### Starting master-bin.000012
|
2009-03-03 21:34:18 +01:00
|
|
|
|
FLUSH LOGS;
|
2011-01-10 14:53:09 +01:00
|
|
|
|
|
2007-06-20 23:11:28 +02:00
|
|
|
|
INSERT INTO t1 VALUES ('0123456789');
|
2011-01-10 14:53:09 +01:00
|
|
|
|
|
|
|
|
|
|
### Starting master-bin.000013
|
2009-03-03 21:34:18 +01:00
|
|
|
|
FLUSH LOGS;
|
2011-01-10 14:53:09 +01:00
|
|
|
|
|
2007-06-20 23:11:28 +02:00
|
|
|
|
DROP TABLE t1;
|
2009-02-19 21:37:40 +01:00
|
|
|
|
|
2013-09-12 20:36:58 +02:00
|
|
|
|
# We create a table named "patch", and load the output into it.
|
|
|
|
|
|
# By using LIKE, we can easily see if the output is missing the '#'
|
|
|
|
|
|
# character, as described in the bug.
|
2009-02-19 21:37:40 +01:00
|
|
|
|
|
2009-03-05 14:35:03 +01:00
|
|
|
|
--disable_query_log
|
|
|
|
|
|
CREATE TABLE patch (a BLOB);
|
2009-02-20 00:24:25 +01:00
|
|
|
|
--exec $MYSQL_BINLOG --hexdump --local-load=$MYSQLTEST_VARDIR/tmp/ $MYSQLD_DATADIR/master-bin.000012 > $MYSQLTEST_VARDIR/tmp/mysqlbinlog_tmp.dat
|
2011-10-19 21:45:18 +02:00
|
|
|
|
### Starting master-bin.000014
|
2009-02-19 21:37:40 +01:00
|
|
|
|
eval LOAD DATA LOCAL INFILE '$MYSQLTEST_VARDIR/tmp/mysqlbinlog_tmp.dat'
|
2013-09-12 20:36:58 +02:00
|
|
|
|
INTO TABLE patch FIELDS TERMINATED BY '';
|
2009-02-19 21:37:40 +01:00
|
|
|
|
--remove_file $MYSQLTEST_VARDIR/tmp/mysqlbinlog_tmp.dat
|
|
|
|
|
|
--enable_query_log
|
|
|
|
|
|
|
2013-03-26 10:35:34 +01:00
|
|
|
|
--echo We expect this value to be 2 (one for the INSERT, one for COMMIT).
|
2009-02-19 21:37:40 +01:00
|
|
|
|
--echo The bug being tested was that 'Query' lines were not preceded by '#'
|
|
|
|
|
|
--echo If the line is in the table, it had to have been preceded by a '#'
|
|
|
|
|
|
--echo
|
2013-09-12 20:36:58 +02:00
|
|
|
|
SELECT COUNT(*) AS `BUG#28293_expect_2` FROM patch WHERE a LIKE '#%Query%';
|
2009-02-19 21:37:40 +01:00
|
|
|
|
DROP TABLE patch;
|
2007-06-20 23:11:28 +02:00
|
|
|
|
|
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
Problem: using "mysqlbinlog | mysql" for recoveries the connection_id()
result may differ from what was used when issuing the statement.
Fix: if there is a connection_id() in a statement, write to binlog
SET pseudo_thread_id= XXX; before it and use the value later on.
mysql-test/r/mysqlbinlog.result:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- test result.
mysql-test/t/mysqlbinlog.test:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- test case.
sql/item_create.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- set thread_specific_used flag for the connection_id() function.
sql/item_func.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- always return thd->variables.pseudo_thread_id as a connection_id()
result, as it contains a proper value for both master and slave.
sql/log_event.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- set LOG_EVENT_THREAD_SPECIFIC_F event flag if thread_specific_used
is set.
sql/sql_class.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- thd->thread_specific_used introduced, which is set if thread specific
value(s) used in a statement.
sql/sql_class.h:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- thd->thread_specific_used introduced, which is set if thread specific
value(s) used in a statement.
2007-08-01 12:27:03 +02:00
|
|
|
|
#
|
2009-03-03 21:34:18 +01:00
|
|
|
|
# Bug#29928 incorrect connection_id() restoring from mysqlbinlog out
|
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
Problem: using "mysqlbinlog | mysql" for recoveries the connection_id()
result may differ from what was used when issuing the statement.
Fix: if there is a connection_id() in a statement, write to binlog
SET pseudo_thread_id= XXX; before it and use the value later on.
mysql-test/r/mysqlbinlog.result:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- test result.
mysql-test/t/mysqlbinlog.test:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- test case.
sql/item_create.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- set thread_specific_used flag for the connection_id() function.
sql/item_func.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- always return thd->variables.pseudo_thread_id as a connection_id()
result, as it contains a proper value for both master and slave.
sql/log_event.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- set LOG_EVENT_THREAD_SPECIFIC_F event flag if thread_specific_used
is set.
sql/sql_class.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- thd->thread_specific_used introduced, which is set if thread specific
value(s) used in a statement.
sql/sql_class.h:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- thd->thread_specific_used introduced, which is set if thread specific
value(s) used in a statement.
2007-08-01 12:27:03 +02:00
|
|
|
|
#
|
2011-10-19 21:45:18 +02:00
|
|
|
|
### Starting master-bin.000015
|
2009-03-03 21:34:18 +01:00
|
|
|
|
FLUSH LOGS;
|
2011-01-10 14:53:09 +01:00
|
|
|
|
|
2009-03-03 21:34:18 +01:00
|
|
|
|
CREATE TABLE t1(a INT);
|
|
|
|
|
|
INSERT INTO t1 VALUES(connection_id());
|
|
|
|
|
|
let $a= `SELECT a FROM t1`;
|
2011-01-10 14:53:09 +01:00
|
|
|
|
|
2011-10-19 21:45:18 +02:00
|
|
|
|
### Starting master-bin.000016
|
2009-03-03 21:34:18 +01:00
|
|
|
|
FLUSH LOGS;
|
2011-01-10 14:53:09 +01:00
|
|
|
|
|
2009-03-06 15:56:17 +01:00
|
|
|
|
let $outfile= $MYSQLTEST_VARDIR/tmp/bug29928.sql;
|
2009-11-03 20:02:56 +01:00
|
|
|
|
--exec $MYSQL_BINLOG $MYSQLD_DATADIR/master-bin.000015 > $outfile
|
2009-03-03 21:34:18 +01:00
|
|
|
|
DROP TABLE t1;
|
|
|
|
|
|
connect (con1, localhost, root, , test);
|
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
Problem: using "mysqlbinlog | mysql" for recoveries the connection_id()
result may differ from what was used when issuing the statement.
Fix: if there is a connection_id() in a statement, write to binlog
SET pseudo_thread_id= XXX; before it and use the value later on.
mysql-test/r/mysqlbinlog.result:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- test result.
mysql-test/t/mysqlbinlog.test:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- test case.
sql/item_create.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- set thread_specific_used flag for the connection_id() function.
sql/item_func.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- always return thd->variables.pseudo_thread_id as a connection_id()
result, as it contains a proper value for both master and slave.
sql/log_event.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- set LOG_EVENT_THREAD_SPECIFIC_F event flag if thread_specific_used
is set.
sql/sql_class.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- thd->thread_specific_used introduced, which is set if thread specific
value(s) used in a statement.
sql/sql_class.h:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- thd->thread_specific_used introduced, which is set if thread specific
value(s) used in a statement.
2007-08-01 12:27:03 +02:00
|
|
|
|
connection con1;
|
2009-03-06 15:56:17 +01:00
|
|
|
|
--exec $MYSQL test < $outfile
|
|
|
|
|
|
--remove_file $outfile
|
2009-03-03 21:34:18 +01:00
|
|
|
|
let $b= `SELECT a FROM t1`;
|
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
Problem: using "mysqlbinlog | mysql" for recoveries the connection_id()
result may differ from what was used when issuing the statement.
Fix: if there is a connection_id() in a statement, write to binlog
SET pseudo_thread_id= XXX; before it and use the value later on.
mysql-test/r/mysqlbinlog.result:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- test result.
mysql-test/t/mysqlbinlog.test:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- test case.
sql/item_create.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- set thread_specific_used flag for the connection_id() function.
sql/item_func.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- always return thd->variables.pseudo_thread_id as a connection_id()
result, as it contains a proper value for both master and slave.
sql/log_event.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- set LOG_EVENT_THREAD_SPECIFIC_F event flag if thread_specific_used
is set.
sql/sql_class.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- thd->thread_specific_used introduced, which is set if thread specific
value(s) used in a statement.
sql/sql_class.h:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- thd->thread_specific_used introduced, which is set if thread specific
value(s) used in a statement.
2007-08-01 12:27:03 +02:00
|
|
|
|
disconnect con1;
|
|
|
|
|
|
connection default;
|
2009-03-03 21:34:18 +01:00
|
|
|
|
let $c= `SELECT $a=$b`;
|
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
Problem: using "mysqlbinlog | mysql" for recoveries the connection_id()
result may differ from what was used when issuing the statement.
Fix: if there is a connection_id() in a statement, write to binlog
SET pseudo_thread_id= XXX; before it and use the value later on.
mysql-test/r/mysqlbinlog.result:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- test result.
mysql-test/t/mysqlbinlog.test:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- test case.
sql/item_create.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- set thread_specific_used flag for the connection_id() function.
sql/item_func.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- always return thd->variables.pseudo_thread_id as a connection_id()
result, as it contains a proper value for both master and slave.
sql/log_event.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- set LOG_EVENT_THREAD_SPECIFIC_F event flag if thread_specific_used
is set.
sql/sql_class.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- thd->thread_specific_used introduced, which is set if thread specific
value(s) used in a statement.
sql/sql_class.h:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- thd->thread_specific_used introduced, which is set if thread specific
value(s) used in a statement.
2007-08-01 12:27:03 +02:00
|
|
|
|
--echo $c
|
2009-03-03 21:34:18 +01:00
|
|
|
|
DROP TABLE t1;
|
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
Problem: using "mysqlbinlog | mysql" for recoveries the connection_id()
result may differ from what was used when issuing the statement.
Fix: if there is a connection_id() in a statement, write to binlog
SET pseudo_thread_id= XXX; before it and use the value later on.
mysql-test/r/mysqlbinlog.result:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- test result.
mysql-test/t/mysqlbinlog.test:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- test case.
sql/item_create.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- set thread_specific_used flag for the connection_id() function.
sql/item_func.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- always return thd->variables.pseudo_thread_id as a connection_id()
result, as it contains a proper value for both master and slave.
sql/log_event.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- set LOG_EVENT_THREAD_SPECIFIC_F event flag if thread_specific_used
is set.
sql/sql_class.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- thd->thread_specific_used introduced, which is set if thread specific
value(s) used in a statement.
sql/sql_class.h:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- thd->thread_specific_used introduced, which is set if thread specific
value(s) used in a statement.
2007-08-01 12:27:03 +02:00
|
|
|
|
|
2007-11-09 13:43:09 +01:00
|
|
|
|
echo shell> mysqlbinlog std_data/corrupt-relay-bin.000624 > var/tmp/bug31793.sql;
|
|
|
|
|
|
error 1;
|
|
|
|
|
|
exec $MYSQL_BINLOG $MYSQL_TEST_DIR/std_data/corrupt-relay-bin.000624 > $MYSQLTEST_VARDIR/tmp/bug31793.sql;
|
2009-03-06 15:56:17 +01:00
|
|
|
|
--remove_file $MYSQLTEST_VARDIR/tmp/bug31793.sql
|
2007-11-09 13:43:09 +01:00
|
|
|
|
|
2006-12-14 11:05:25 +01:00
|
|
|
|
#
|
|
|
|
|
|
# Test --disable-force-if-open and --force-if-open
|
|
|
|
|
|
#
|
2011-10-19 21:45:18 +02:00
|
|
|
|
### Starting master-bin.000017
|
2009-03-06 15:56:17 +01:00
|
|
|
|
FLUSH LOGS;
|
2011-01-10 14:53:09 +01:00
|
|
|
|
|
2006-12-14 11:05:25 +01:00
|
|
|
|
--error 1
|
2009-11-03 20:02:56 +01:00
|
|
|
|
--exec $MYSQL_BINLOG $MYSQLD_DATADIR/master-bin.000017 >/dev/null 2>/dev/null
|
|
|
|
|
|
--exec $MYSQL_BINLOG --force-if-open $MYSQLD_DATADIR/master-bin.000017 >/dev/null 2>/dev/null
|
2006-12-14 11:05:25 +01:00
|
|
|
|
|
2009-03-06 15:56:17 +01:00
|
|
|
|
--echo Bug#31611 Security risk with BINLOG statement
|
2007-11-03 01:33:48 +01:00
|
|
|
|
|
|
|
|
|
|
SET BINLOG_FORMAT=ROW;
|
|
|
|
|
|
CREATE DATABASE mysqltest1;
|
|
|
|
|
|
CREATE USER untrusted@localhost;
|
|
|
|
|
|
GRANT SELECT ON mysqltest1.* TO untrusted@localhost;
|
|
|
|
|
|
|
|
|
|
|
|
SHOW GRANTS FOR untrusted@localhost;
|
|
|
|
|
|
USE mysqltest1;
|
|
|
|
|
|
CREATE TABLE t1 (a INT, b CHAR(64));
|
2011-01-10 14:53:09 +01:00
|
|
|
|
|
2011-10-19 21:45:18 +02:00
|
|
|
|
### Starting master-bin.000018
|
2007-11-03 01:33:48 +01:00
|
|
|
|
flush logs;
|
2011-01-10 14:53:09 +01:00
|
|
|
|
|
2007-11-03 01:33:48 +01:00
|
|
|
|
INSERT INTO t1 VALUES (1,USER());
|
2011-01-10 14:53:09 +01:00
|
|
|
|
|
2011-10-19 21:45:18 +02:00
|
|
|
|
### Starting master-bin.000019
|
2007-11-03 01:33:48 +01:00
|
|
|
|
flush logs;
|
2009-11-03 20:02:56 +01:00
|
|
|
|
echo mysqlbinlog var/log/master-bin.000018 > var/tmp/bug31611.sql;
|
|
|
|
|
|
exec $MYSQL_BINLOG $MYSQLD_DATADIR/master-bin.000018 > $MYSQLTEST_VARDIR/tmp/bug31611.sql;
|
2007-11-03 01:33:48 +01:00
|
|
|
|
connect (unsecure,localhost,untrusted,,mysqltest1);
|
|
|
|
|
|
echo mysql mysqltest1 -uuntrusted < var/tmp/bug31611.sql;
|
|
|
|
|
|
error 1;
|
|
|
|
|
|
exec $MYSQL mysqltest1 -uuntrusted < $MYSQLTEST_VARDIR/tmp/bug31611.sql;
|
2009-03-06 15:56:17 +01:00
|
|
|
|
--remove_file $MYSQLTEST_VARDIR/tmp/bug31611.sql
|
2007-11-03 01:33:48 +01:00
|
|
|
|
connection unsecure;
|
|
|
|
|
|
error ER_TABLEACCESS_DENIED_ERROR;
|
|
|
|
|
|
INSERT INTO t1 VALUES (1,USER());
|
|
|
|
|
|
|
|
|
|
|
|
SELECT * FROM t1;
|
|
|
|
|
|
connection default;
|
|
|
|
|
|
DROP DATABASE mysqltest1;
|
2007-11-12 11:29:55 +01:00
|
|
|
|
DROP USER untrusted@localhost;
|
2007-11-03 01:33:48 +01:00
|
|
|
|
|
2009-03-06 15:56:17 +01:00
|
|
|
|
--echo Bug#32580 mysqlbinlog cannot read binlog event with user variables
|
2007-11-23 14:41:41 +01:00
|
|
|
|
|
|
|
|
|
|
# Testing that various kinds of events can be read and restored properly.
|
|
|
|
|
|
|
|
|
|
|
|
connection default;
|
|
|
|
|
|
USE test;
|
|
|
|
|
|
SET BINLOG_FORMAT = STATEMENT;
|
2011-01-10 14:53:09 +01:00
|
|
|
|
|
2011-10-19 21:45:18 +02:00
|
|
|
|
### Starting master-bin.000020
|
2007-11-23 14:41:41 +01:00
|
|
|
|
FLUSH LOGS;
|
2011-01-10 14:53:09 +01:00
|
|
|
|
|
2007-11-23 14:41:41 +01:00
|
|
|
|
CREATE TABLE t1 (a_real FLOAT, an_int INT, a_decimal DECIMAL(5,2), a_string CHAR(32));
|
|
|
|
|
|
SET @a_real = rand(20) * 1000;
|
|
|
|
|
|
SET @an_int = 1000;
|
|
|
|
|
|
SET @a_decimal = CAST(rand(19) * 999 AS DECIMAL(5,2));
|
|
|
|
|
|
SET @a_string = 'Just a test';
|
|
|
|
|
|
INSERT INTO t1 VALUES (@a_real, @an_int, @a_decimal, @a_string);
|
2011-01-10 14:53:09 +01:00
|
|
|
|
|
2011-10-19 21:45:18 +02:00
|
|
|
|
### Starting master-bin.000021
|
2007-11-23 14:41:41 +01:00
|
|
|
|
FLUSH LOGS;
|
2011-01-10 14:53:09 +01:00
|
|
|
|
|
2007-11-23 14:41:41 +01:00
|
|
|
|
query_vertical SELECT * FROM t1;
|
|
|
|
|
|
DROP TABLE t1;
|
|
|
|
|
|
|
2009-11-03 20:02:56 +01:00
|
|
|
|
echo >> mysqlbinlog var/log/master-bin.000020 > var/tmp/bug32580.sql;
|
|
|
|
|
|
exec $MYSQL_BINLOG $MYSQLD_DATADIR/master-bin.000020 > $MYSQLTEST_VARDIR/tmp/bug32580.sql;
|
2007-11-23 14:41:41 +01:00
|
|
|
|
echo >> mysql test < var/tmp/bug32580.sql;
|
|
|
|
|
|
exec $MYSQL test < $MYSQLTEST_VARDIR/tmp/bug32580.sql;
|
|
|
|
|
|
remove_file $MYSQLTEST_VARDIR/tmp/bug32580.sql;
|
|
|
|
|
|
|
|
|
|
|
|
query_vertical SELECT * FROM t1;
|
|
|
|
|
|
DROP TABLE t1;
|
|
|
|
|
|
|
2009-02-20 12:55:43 +01:00
|
|
|
|
#
|
2009-03-05 14:35:03 +01:00
|
|
|
|
# Bug#37313 BINLOG Contains Incorrect server id
|
2009-02-20 12:55:43 +01:00
|
|
|
|
#
|
|
|
|
|
|
|
2009-03-05 14:35:03 +01:00
|
|
|
|
let $binlog_file= $MYSQLTEST_VARDIR/tmp/mysqlbinlog_bug37313.binlog;
|
|
|
|
|
|
let $save_server_id= `SELECT @@global.server_id`;
|
|
|
|
|
|
let $s_id_max= `SELECT (1 << 32) - 1`;
|
|
|
|
|
|
eval SET @@global.server_id= $s_id_max;
|
2009-02-20 12:55:43 +01:00
|
|
|
|
|
2009-03-05 14:35:03 +01:00
|
|
|
|
RESET MASTER;
|
|
|
|
|
|
FLUSH LOGS;
|
2011-01-10 14:53:09 +01:00
|
|
|
|
|
2009-03-06 15:56:17 +01:00
|
|
|
|
--exec $MYSQL_BINLOG $MYSQLD_DATADIR/master-bin.000001 > $binlog_file
|
2009-02-20 12:55:43 +01:00
|
|
|
|
--replace_result $MYSQLTEST_VARDIR MYSQLTEST_VARDIR
|
2009-03-05 14:35:03 +01:00
|
|
|
|
eval SELECT
|
|
|
|
|
|
(@a:=LOAD_FILE("$binlog_file"))
|
|
|
|
|
|
IS NOT NULL;
|
|
|
|
|
|
let $s_id_unsigned= `SELECT @a LIKE "%server id $s_id_max%" /* must return 1 */`;
|
2009-02-20 12:55:43 +01:00
|
|
|
|
echo *** Unsigned server_id $s_id_max is found: $s_id_unsigned ***;
|
|
|
|
|
|
|
2009-03-05 14:35:03 +01:00
|
|
|
|
eval SET @@global.server_id= $save_server_id;
|
|
|
|
|
|
--remove_file $binlog_file
|
2009-02-20 12:55:43 +01:00
|
|
|
|
|
2009-05-07 16:31:02 +02:00
|
|
|
|
#
|
|
|
|
|
|
# Bug #41943: mysqlbinlog.exe crashes if --hexdump option is used
|
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
|
|
RESET MASTER;
|
|
|
|
|
|
FLUSH LOGS;
|
|
|
|
|
|
|
|
|
|
|
|
# We do not need the results, just make sure that mysqlbinlog does not crash
|
|
|
|
|
|
--exec $MYSQL_BINLOG --hexdump --read-from-remote-server --user=root --host=127.0.0.1 --port=$MASTER_MYPORT master-bin.000001 >/dev/null
|
|
|
|
|
|
|
2009-09-30 04:01:52 +02:00
|
|
|
|
#
|
|
|
|
|
|
# #46998
|
|
|
|
|
|
# This test verifies if the 'BEGIN', 'COMMIT' and 'ROLLBACK' are output
|
|
|
|
|
|
# in regardless of database filtering
|
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
|
|
RESET MASTER;
|
|
|
|
|
|
FLUSH LOGS;
|
|
|
|
|
|
|
|
|
|
|
|
# The following three test cases were wrtten into binlog_transaction.000001
|
|
|
|
|
|
# Test case1: Test if the 'BEGIN' and 'COMMIT' are output for the 'test' database
|
|
|
|
|
|
# in transaction1 base on innodb engine tables
|
|
|
|
|
|
# use test;
|
|
|
|
|
|
# create table t1(a int) engine= innodb;
|
|
|
|
|
|
# use mysql;
|
|
|
|
|
|
# create table t2(a int) engine= innodb;
|
|
|
|
|
|
# Transaction1 begin
|
|
|
|
|
|
# begin;
|
|
|
|
|
|
# use test;
|
|
|
|
|
|
# insert into t1 (a) values (1);
|
|
|
|
|
|
# use mysql;
|
|
|
|
|
|
# insert into t2 (a) values (1);
|
|
|
|
|
|
# commit;
|
|
|
|
|
|
# Transaction1 end
|
|
|
|
|
|
|
|
|
|
|
|
# Test case2: Test if the 'BEGIN' and 'ROLLBACK' are output for the 'test' database
|
|
|
|
|
|
# in transaction2 base on innodb and myisam engine tables
|
|
|
|
|
|
# use test;
|
|
|
|
|
|
# create table t3(a int) engine= innodb;
|
|
|
|
|
|
# use mysql;
|
|
|
|
|
|
# create table t4(a int) engine= myisam;
|
|
|
|
|
|
# Transaction2 begin
|
|
|
|
|
|
# begin;
|
|
|
|
|
|
# use test;
|
|
|
|
|
|
# insert into t3 (a) values (2);
|
|
|
|
|
|
# use mysql;
|
|
|
|
|
|
# insert into t4 (a) values (2);
|
|
|
|
|
|
# rollback;
|
|
|
|
|
|
# Transaction2 end
|
|
|
|
|
|
|
|
|
|
|
|
--echo #
|
2010-03-28 13:57:33 +02:00
|
|
|
|
--echo # Test if the 'BEGIN', 'ROLLBACK' and 'COMMIT' are output if the database specified exists
|
2009-09-30 04:31:25 +02:00
|
|
|
|
--exec $MYSQL_BINLOG --database=test --short-form $MYSQLTEST_VARDIR/std_data/binlog_transaction.000001
|
2009-09-30 04:01:52 +02:00
|
|
|
|
--echo #
|
2010-03-28 13:57:33 +02:00
|
|
|
|
--echo # Test if the 'BEGIN', 'ROLLBACK' and 'COMMIT' are output if the database specified does not exist
|
2009-09-30 04:31:25 +02:00
|
|
|
|
--exec $MYSQL_BINLOG --database=not_exist --short-form $MYSQLTEST_VARDIR/std_data/binlog_transaction.000001
|
2009-09-30 04:01:52 +02:00
|
|
|
|
|
2010-03-28 13:57:33 +02:00
|
|
|
|
--echo #
|
|
|
|
|
|
--echo # Test if the 'SAVEPOINT', 'ROLLBACK TO' are output if the database specified exists
|
|
|
|
|
|
--exec $MYSQL_BINLOG --database=db1 --short-form $MYSQLTEST_VARDIR/std_data/binlog_savepoint.000001
|
|
|
|
|
|
--echo #
|
|
|
|
|
|
--echo # Test if the 'SAVEPOINT', 'ROLLBACK TO' are output if the database specified does not exist
|
|
|
|
|
|
--exec $MYSQL_BINLOG --database=not_exist --short-form $MYSQLTEST_VARDIR/std_data/binlog_savepoint.000001
|
|
|
|
|
|
|
2007-02-19 11:57:06 +01:00
|
|
|
|
--echo End of 5.0 tests
|
2009-05-08 19:24:15 +02:00
|
|
|
|
|
2007-03-07 07:21:24 +01:00
|
|
|
|
--echo End of 5.1 tests
|
2009-10-02 10:18:40 +02:00
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
|
# BUG#38468 Memory leak detected when using mysqlbinlog utility;
|
|
|
|
|
|
#
|
|
|
|
|
|
disable_query_log;
|
|
|
|
|
|
RESET MASTER;
|
|
|
|
|
|
CREATE TABLE t1 SELECT 1;
|
|
|
|
|
|
FLUSH LOGS;
|
|
|
|
|
|
DROP TABLE t1;
|
|
|
|
|
|
enable_query_log;
|
|
|
|
|
|
|
|
|
|
|
|
# Write an empty file for comparison
|
|
|
|
|
|
write_file $MYSQLTEST_VARDIR/tmp/mysqlbinlog.warn.empty;
|
|
|
|
|
|
EOF
|
|
|
|
|
|
|
|
|
|
|
|
# Before fix of BUG#38468, this would generate some warnings
|
|
|
|
|
|
--exec $MYSQL_BINLOG $MYSQLD_DATADIR/master-bin.000001 >/dev/null 2> $MYSQLTEST_VARDIR/tmp/mysqlbinlog.warn
|
|
|
|
|
|
|
|
|
|
|
|
# Make sure the command above does not generate any error or warnings
|
|
|
|
|
|
diff_files $MYSQLTEST_VARDIR/tmp/mysqlbinlog.warn $MYSQLTEST_VARDIR/tmp/mysqlbinlog.warn.empty;
|
|
|
|
|
|
|
|
|
|
|
|
# Cleanup for this part of test
|
|
|
|
|
|
remove_file $MYSQLTEST_VARDIR/tmp/mysqlbinlog.warn.empty;
|
|
|
|
|
|
remove_file $MYSQLTEST_VARDIR/tmp/mysqlbinlog.warn;
|
2010-10-29 16:56:58 +02:00
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
|
# WL#5625: Deprecate mysqlbinlog options --base64-output=always and --base64-output
|
|
|
|
|
|
#
|
|
|
|
|
|
--echo # Expect deprecation warning.
|
|
|
|
|
|
--exec $MYSQL_BINLOG --base64-output=always std_data/master-bin.000001 > /dev/null 2> $MYSQLTEST_VARDIR/tmp/mysqlbinlog.warn
|
|
|
|
|
|
--cat_file $MYSQLTEST_VARDIR/tmp/mysqlbinlog.warn
|
|
|
|
|
|
|
|
|
|
|
|
--echo # Expect deprecation warning again.
|
|
|
|
|
|
--exec $MYSQL_BINLOG --base64-output std_data/master-bin.000001 > /dev/null 2> $MYSQLTEST_VARDIR/tmp/mysqlbinlog.warn
|
|
|
|
|
|
--cat_file $MYSQLTEST_VARDIR/tmp/mysqlbinlog.warn
|
|
|
|
|
|
|
|
|
|
|
|
# Clean up this part of the test.
|
|
|
|
|
|
--remove_file $MYSQLTEST_VARDIR/tmp/mysqlbinlog.warn
|
2010-12-29 06:22:52 +01:00
|
|
|
|
|
2010-12-29 04:52:57 +01:00
|
|
|
|
# BUG#50914
|
|
|
|
|
|
# This test verifies if the approach of the mysqlbinlog prints
|
|
|
|
|
|
# "use $database" statements to its output stream will cause
|
|
|
|
|
|
# "No Database Selected" error when dropping and recreating
|
|
|
|
|
|
# that database.
|
|
|
|
|
|
#
|
|
|
|
|
|
RESET MASTER;
|
|
|
|
|
|
CREATE DATABASE test1;
|
|
|
|
|
|
USE test1;
|
|
|
|
|
|
CREATE TABLE t1(id int);
|
|
|
|
|
|
DROP DATABASE test1;
|
|
|
|
|
|
CREATE DATABASE test1;
|
|
|
|
|
|
USE test1;
|
|
|
|
|
|
CREATE TABLE t1(id int);
|
|
|
|
|
|
DROP TABLE t1;
|
|
|
|
|
|
DROP DATABASE test1;
|
|
|
|
|
|
let $master_binlog= query_get_value(SHOW MASTER STATUS, File, 1);
|
|
|
|
|
|
FLUSH LOGS;
|
2014-12-22 01:02:38 +01:00
|
|
|
|
--source include/wait_for_binlog_checkpoint.inc
|
2010-12-29 04:52:57 +01:00
|
|
|
|
|
|
|
|
|
|
let $MYSQLD_DATADIR= `SELECT @@datadir`;
|
|
|
|
|
|
exec $MYSQL_BINLOG $MYSQLD_DATADIR/$master_binlog | $MYSQL test 2>&1;
|
|
|
|
|
|
|
|
|
|
|
|
let $binlog_file= query_get_value(SHOW MASTER STATUS, File, 1);
|
|
|
|
|
|
source include/show_binlog_events.inc;
|
|
|
|
|
|
|
2011-03-25 15:16:13 +01:00
|
|
|
|
#
|
|
|
|
|
|
# BUG#11766427 BUG#59530: Filter by server id in mysqlbinlog fails
|
|
|
|
|
|
# This test checks that the format description log event is not
|
|
|
|
|
|
# filtered out by the --server-id option.
|
|
|
|
|
|
#
|
|
|
|
|
|
RESET MASTER;
|
|
|
|
|
|
USE test;
|
|
|
|
|
|
CREATE TABLE t1 (a INT);
|
|
|
|
|
|
--let $old_server_id= `SELECT @@GLOBAL.SERVER_ID`
|
|
|
|
|
|
SET GLOBAL SERVER_ID = 2;
|
|
|
|
|
|
DROP TABLE t1;
|
|
|
|
|
|
--let $master_binlog= query_get_value(SHOW MASTER STATUS, File, 1)
|
|
|
|
|
|
FLUSH LOGS;
|
|
|
|
|
|
# The following should only create t1, not drop it.
|
|
|
|
|
|
--exec $MYSQL_BINLOG --server-id=1 $MYSQLD_DATADIR/$master_binlog | $MYSQL
|
|
|
|
|
|
SHOW TABLES IN test;
|
|
|
|
|
|
# The following should only drop t1, not create it.
|
|
|
|
|
|
--exec $MYSQL_BINLOG --server-id=2 $MYSQLD_DATADIR/$master_binlog | $MYSQL
|
|
|
|
|
|
SHOW TABLES IN test;
|
|
|
|
|
|
eval SET GLOBAL SERVER_ID = $old_server_id;
|
2013-09-12 20:36:58 +02:00
|
|
|
|
|
|
|
|
|
|
--echo #
|
|
|
|
|
|
--echo # MDEV-4645: Incorrect reads of frozen binlog events;
|
|
|
|
|
|
--echo # FDE corrupted in relay log
|
|
|
|
|
|
--echo #
|
2013-09-25 19:41:41 +02:00
|
|
|
|
--let TZ=GMT
|
2013-09-12 20:36:58 +02:00
|
|
|
|
--exec $MYSQL_BINLOG --hexdump std_data/mdev-4645-binlog_checksum.binlog
|
|
|
|
|
|
--exec $MYSQL_BINLOG --hexdump std_data/mdev-4645-binlog_group_id.binlog
|
|
|
|
|
|
--exec $MYSQL_BINLOG --hexdump std_data/mdev-4645-binlog_group_id_checksum.binlog
|
|
|
|
|
|
--exec $MYSQL_BINLOG --hexdump std_data/mdev-4645-binlog_none.binlog
|
2017-11-03 12:33:01 +01:00
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
|
# MDEV-12372 mysqlbinlog --version output is the same on 10.x as on 5.5.x, and contains not only version
|
|
|
|
|
|
#
|
|
|
|
|
|
replace_regex /.*mysqlbinlog(\.exe)? Ver .* for .* at [-_a-zA-Z0-9]+/mysqlbinlog Ver VER for OS at ARCH/;
|
|
|
|
|
|
exec $MYSQL_BINLOG --version;
|