Vasil Dimov
912750f2d2
Merge mysql-5.1 into mysql-5.1-innodb
2010-05-11 13:41:34 +03:00
Inaam Rana
a6226390cc
Undo the changes made by Vasil in sys_vars/all_vars when adjusting
...
for the new parameters introduced in the plugin 1.1. Now that we have
basic tests for all these new parameters it is no longer needed to
adjust the all_vars.result file.
2010-05-10 17:44:40 -04:00
Mattias Jonsson
6fa04cad8f
merge
2010-05-10 15:17:06 +02:00
Marko Makela
82009da5a8
Merge from mysql-5.1-innodb:
...
------------------------------------------------------------
revno: 3454
committer: Marko Makela <mmakela@bk-internal.mysql.com>
branch nick: mysql-5.1-innodb
timestamp: Mon 2010-05-10 13:37:52 +0200
message:
Add an innodb test case for Bug #49164 .
2010-05-10 15:14:45 +02:00
Marko Makela
dcdb8f82b3
Add an innodb_plugin test case for Bug #49164 .
2010-05-10 13:38:25 +02:00
Marko Makela
6b062319d4
Add an innodb test case for Bug #49164 .
2010-05-10 13:37:52 +02:00
Alfranio Correia
209cccf55d
BUG#49019 Mixing self-logging eng. and regular eng. does not switch to row in mixed mode
...
Backport of the patch for 5.1-bugteam.
2010-05-09 23:45:25 +01:00
Alexey Kopytov
5ef2bdea81
Manual merge of mysql-5.1-bugteam to mysql-trunk-merge.
...
Conflicts:
Text conflict in mysql-test/r/grant.result
Text conflict in mysql-test/t/grant.test
Text conflict in mysys/mf_loadpath.c
Text conflict in sql/slave.cc
Text conflict in sql/sql_priv.h
2010-05-09 02:03:35 +04:00
Luis Soares
2646306cc9
BUG#49522: Replication problem with mixed MyISAM/InnoDB
...
When using a non-transactional table (t1) on the master
and with autocommit disabled, no COMMIT is recorded
in the binary log ending the statement. Therefore, if
the slave has t1 in a transactional engine, then it will
be as if a transaction is started but never ends. This is
actually BUG#29288 all over again.
We fix this by cherrypicking the cset for BUG#29288 which
was pushed to a later mysql version. The revision picked
was: mats@sun.com-20090923094343-bnheplq8n95opjay .
Additionally, a test case for covering the scenario depicted
in the bug report is included in this cset.
2010-05-07 18:48:35 +01:00
Konstantin Osipov
946fad3502
Draft patch that fixes and a sketches test cases for:
...
Bug#20837 Apparent change of isolation level during transaction,
Bug#46527 COMMIT AND CHAIN RELEASE does not make sense,
Bug#53343 completion_type=1, COMMIT/ROLLBACK AND CHAIN don't
preserve the isolation level
Bug#53346 completion_type has strange effect in a stored
procedure/prepared statement
Make thd->tx_isolation mean strictly "current transaction
isolation level"
Make thd->variables.tx_isolation mean "current session isolation
level".
The current transaction isolation level is now established
at transaction start. If there was a SET TRANSACTION
ISOLATION LEVEL statement, the value is taken from it.
Otherwise, the session value is used.
A change in a session value, made while a transaction is active,
whereas still allowed, no longer has any effect on the
current transaction isolation level. This is an incompatible
change.
A change in a session isolation level, made while there is
no active transaction, overrides SET TRANSACTION statement,
if there was any.
Changed the impelmentation to not look at @@session.completion_type
in the parser, and thus fixed Bug#53346.
Changed the parser to not allow AND NO CHAIN RELEASE,
and thus fixed Bug#46527.
Changed the transaction API to take the current transaction
isolation level into account:
- BEGIN/COMMIT now do preserve the current transaction
isolation level if chaining is on.
- implicit commit, XA COMMIT or XA ROLLBACK or autocommit don't.
2010-05-07 20:28:59 +04:00
Alexey Kopytov
e58c059695
Manual merge of local mysql-trunk-merge with bk-internal.
...
Conflicts:
Text conflict in sql/CMakeLists.txt
2010-05-07 18:56:46 +04:00
Alexander Nozdrin
783c6acd7f
Fix merge error: update test result file.
2010-05-07 15:10:40 +04:00
Alexander Nozdrin
762b535de2
Manual merge from mysql-trunk.
...
Conflicts:
- mysql-test/suite/engines/funcs/t/disabled.def
- mysql-test/suite/engines/iuds/t/disabled.def
- mysql-test/suite/engines/iuds/t/insert_number.test
2010-05-07 13:37:16 +04:00
Marko Mäkelä
326d75bd41
Merge a contribution from Ryan Mack at Facebook:
...
Bugfix for 53290, fast unique index creation fails on duplicate null values
Summary:
Bug in the fast index creation code incorrectly considers null
values to be duplicates during block merging. Innodb policy is that
multiple null values are allowed in a unique index. Null duplicates
were correctly ignored while sorting individual blocks and with slow
index creation.
Test Plan:
mtr, including new test, load dbs using deferred index creation
DiffCamp Revision: 110840
Reviewed By: mcallaghan
CC: mcallaghan, mysql-devel@lists
Revert Plan:
OK
2010-05-05 15:39:01 +03:00
Marko Mäkelä
b7ee1e6447
Merge from mysql-5.1-innodb:
...
------------------------------------------------------------
revno: 3449
revision-id: marko.makela@oracle.com-20100505104425-39y6qbffgotrhck2
parent: marko.makela@oracle.com-20100505104001-883pqiepo384qr5h
committer: Marko Mäkelä <marko.makela@oracle.com>
branch nick: 5.1-innodb
timestamp: Wed 2010-05-05 13:44:25 +0300
message:
Factor out innodb_multi_update.test from innodb.test
2010-05-05 14:03:14 +03:00
Marko Mäkelä
415e5b282b
Factor out innodb_multi_update.test from innodb.test
2010-05-05 13:44:25 +03:00
Marko Mäkelä
e73feed2d8
Factor out innodb_multi_update.test from innodb.test
2010-05-05 13:40:01 +03:00
Vasil Dimov
e4bf42a10a
Fix path to include file in innodb_bug52745.test
2010-05-05 13:13:58 +03:00
Vasil Dimov
eede696ad8
Fix path to include file.
2010-05-05 13:13:05 +03:00
Horst.Hunger
9eae31abc4
Patch for 47759 to trunk-bugfixing.
2010-05-05 09:35:38 +02:00
Omer BarNir
fb47b30384
Updates to README file of the 'engines' test suites
2010-05-04 14:24:36 -07:00
Omer BarNir
8372ce979d
Changes to result files in the engine suite - missed from previous commit
2010-05-04 13:39:17 -07:00
Andrei Elkin
efcc90b6eb
Bug #50942 mix_innodb_myisam_side_effects.test is not deterministic
...
The test was used to fail because of
UPDATE t3,t4 SET t3.a=t4.a + bug27417(1);
did not prescribe the order of two row operations implied by the update.
Fixed with forcing the order with adding a where condition w/o
affecting the former bug fixes logics.
mysql-test/extra/binlog_tests/mix_innodb_myisam_side_effects.test:
implemented the bug page suggestion to make a test deterministic.
mysql-test/suite/binlog/r/binlog_row_mix_innodb_myisam.result:
results are updated and (!) corrected.
mysql-test/suite/binlog/r/binlog_stm_mix_innodb_myisam.result:
results are updated
2010-05-04 22:31:49 +03:00
Omer BarNir
8ac23986e7
Updates to test and result files in the 'engine' suites following changes in 5.5
2010-05-04 11:10:17 -07:00
Marko Mäkelä
304daa7431
fsp_init_file_page_low(): Zero out the page. (Bug #53306 )
2010-05-04 16:13:58 +03:00
Mattias Jonsson
f33075fd16
merge
2010-05-04 14:26:44 +02:00
Vasil Dimov
a5db3eff62
Merge from mysql-5.1-innodb:
...
------------------------------------------------------------
revno: 3419
revision-id: marko.makela@oracle.com-20100426110856-14tc8re1f5kp5j3g
parent: marko.makela@oracle.com-20100426105215-2e9nzq8z0nfwxjky
committer: Marko M?kel? <marko.makela@oracle.com>
branch nick: 5.1-innodb
timestamp: Mon 2010-04-26 14:08:56 +0300
message:
Add a test case for Bug #52745 .
added:
mysql-test/suite/innodb_plugin/r/innodb_bug52745.result innodb_bug52745.resu-20100426110444-2211220xcgz0el4v-1
mysql-test/suite/innodb_plugin/t/innodb_bug52745.test innodb_bug52745.test-20100426110444-2211220xcgz0el4v-2
------------------------------------------------------------
2010-05-04 13:15:46 +03:00
Vasil Dimov
f18d97ace8
Merge from mysql-5.1-innodb:
...
------------------------------------------------------------
revno: 3417
revision-id: marko.makela@oracle.com-20100426102725-as2vc44ddykg1786
parent: marko.makela@oracle.com-20100426073949-txnbqldrl9fdlapx
committer: Marko M?kel? <marko.makela@oracle.com>
branch nick: 5.1-innodb
timestamp: Mon 2010-04-26 13:27:25 +0300
message:
row_search_for_mysql(): Never try semi-consistent read in unique searches.
They are only useful in table scans. (Bug #52663 )
added:
mysql-test/suite/innodb/r/innodb_bug52663.result innodb_bug52663.resu-20100426102328-fymyevkummgyc3gm-1
mysql-test/suite/innodb/t/innodb_bug52663-master.opt innodb_bug52663maste-20100426102328-fymyevkummgyc3gm-2
mysql-test/suite/innodb/t/innodb_bug52663.test innodb_bug52663.test-20100426102328-fymyevkummgyc3gm-3
mysql-test/suite/innodb_plugin/r/innodb_bug52663.result innodb_bug52663.resu-20100426102328-fymyevkummgyc3gm-4
mysql-test/suite/innodb_plugin/t/innodb_bug52663.test innodb_bug52663.test-20100426102328-fymyevkummgyc3gm-5
modified:
storage/innobase/row/row0sel.c 2@cee13dc7-1704-0410-992b-c9b4543f1246:trunk%2Frow%2Frow0sel.c
storage/innodb_plugin/ChangeLog 2425@16c675df-0fcb-4bc9-8058-dcc011a37293:branches%2Fzip%2FChangeLog
storage/innodb_plugin/row/row0sel.c 2@16c675df-0fcb-4bc9-8058-dcc011a37293:trunk%2Frow%2Frow0sel.c
------------------------------------------------------------
2010-05-04 12:51:25 +03:00
Vasil Dimov
08c8407439
Merge from mysql-5.1-innodb:
...
------------------------------------------------------------
revno: 3415
revision-id: calvin.sun@oracle.com-20100422191614-2atswbilyyxep6rm
parent: marko.makela@oracle.com-20100422093342-jf9ojlzdqsdebohn
committer: Calvin Sun <calvin.sun@oracle.com>
branch nick: mysql-5.1-innodb
timestamp: Thu 2010-04-22 14:16:14 -0500
message:
mysql-5.1-innodb: add error codes to innodb_bug51920.test
kill of active connection yields different error code
depending on platform.
modified:
mysql-test/suite/innodb/r/innodb_bug51920.result 6918@cee13dc7-1704-0410-992b-c9b4543f1246:branches%2F5.1%2Fmysql-test%2Finnodb_bug51920.result
mysql-test/suite/innodb/t/innodb_bug51920.test 6918@cee13dc7-1704-0410-992b-c9b4543f1246:branches%2F5.1%2Fmysql-test%2Finnodb_bug51920.test
mysql-test/suite/innodb_plugin/r/innodb_bug51920.result 6919@16c675df-0fcb-4bc9-8058-dcc011a37293:branches%2Fzip%2Fmysql-test%2Finnodb_bug51920.result
mysql-test/suite/innodb_plugin/t/innodb_bug51920.test 6919@16c675df-0fcb-4bc9-8058-dcc011a37293:branches%2Fzip%2Fmysql-test%2Finnodb_bug51920.test
------------------------------------------------------------
2010-05-04 12:40:41 +03:00
Inaam Rana
22b4c120d3
pull changes from parent
2010-05-03 12:21:10 -04:00
Georgi Kodinov
e038b56dab
merged 5.1-innodb
2010-05-01 19:12:12 +03:00
Sunny Bains
f232dfbf82
Fix failing tests.
2010-05-01 07:54:14 +10:00
Vasil Dimov
3bffc40a24
Disable innodb.innodb, main.ps_3innodb and main.partition_innodb_plugin
...
mysql-tests because those emit (spurious?) valgrind warnings.
2010-04-30 13:02:36 +03:00
Alexey Kopytov
85ed11c60d
Manual merge of mysql-5.1-bugteam to mysql-trunk-merge.
...
Conflicts:
Text conflict in configure.in
Text conflict in dbug/dbug.c
Text conflict in mysql-test/r/ps.result
Text conflict in mysql-test/t/ps.test
Text conflict in sql/CMakeLists.txt
Text conflict in sql/ha_ndbcluster.cc
Text conflict in sql/mysqld.cc
Text conflict in sql/sql_plugin.cc
Text conflict in sql/sql_table.cc
2010-04-30 00:33:06 +04:00
Inaam Rana
cfbce98a00
Add basic tests for new innodb features
2010-04-29 13:43:10 -04:00
Sven Sandberg
cf5ebc5821
BUG#50670: Slave stops with error code 1644
...
Clarified error messages related to unsafe statements:
- avoid the internal technical term "row injection"
- use 'binary log' instead of 'binlog'
- avoid the word 'unsafeness'
mysql-test/extra/binlog_tests/blackhole.test:
updated suppression pattern
mysql-test/extra/binlog_tests/mix_innodb_myisam_binlog.test:
updated suppression pattern
mysql-test/extra/rpl_tests/rpl_binlog_max_cache_size.test:
updated suppression pattern
mysql-test/extra/rpl_tests/rpl_insert_id.test:
updated suppression pattern
mysql-test/extra/rpl_tests/rpl_loaddata.test:
updated suppression pattern
mysql-test/extra/rpl_tests/rpl_mixing_engines.test:
updated suppression pattern
mysql-test/extra/rpl_tests/rpl_start_stop_slave.test:
updated suppression pattern
mysql-test/extra/rpl_tests/rpl_stm_000001.test:
updated suppression pattern
mysql-test/extra/rpl_tests/rpl_stop_middle_group.test:
updated suppression pattern
mysql-test/r/archive.result:
updated result file
mysql-test/r/commit_1innodb.result:
updated result file
mysql-test/r/ctype_cp932_binlog_stm.result:
updated result file
mysql-test/r/partition_innodb_stmt.result:
updated result file
mysql-test/suite/binlog/r/binlog_innodb.result:
updated result file
mysql-test/suite/binlog/r/binlog_killed.result:
updated result file
mysql-test/suite/binlog/r/binlog_multi_engine.result:
updated result file
mysql-test/suite/binlog/r/binlog_row_mix_innodb_myisam.result:
updated result file
mysql-test/suite/binlog/r/binlog_statement_insert_delayed.result:
updated result file
mysql-test/suite/binlog/r/binlog_stm_blackhole.result:
updated result file
mysql-test/suite/binlog/r/binlog_stm_do_db.result:
updated result file
mysql-test/suite/binlog/r/binlog_stm_mix_innodb_myisam.result:
updated result file
mysql-test/suite/binlog/r/binlog_stm_ps.result:
updated result file
mysql-test/suite/binlog/r/binlog_stm_row.result:
updated result file
mysql-test/suite/binlog/r/binlog_stm_unsafe_warning.result:
updated result file
mysql-test/suite/binlog/r/binlog_unsafe.result:
updated result file
mysql-test/suite/binlog/t/binlog_killed.test:
updated suppression pattern
mysql-test/suite/binlog/t/binlog_multi_engine.test:
updated suppression pattern
mysql-test/suite/binlog/t/binlog_statement_insert_delayed.test:
updated suppression pattern
mysql-test/suite/binlog/t/binlog_stm_ps.test:
updated suppression pattern
mysql-test/suite/binlog/t/binlog_stm_row.test:
updated suppression pattern
mysql-test/suite/binlog/t/binlog_stm_unsafe_warning.test:
updated suppression pattern
mysql-test/suite/binlog/t/binlog_tmp_table.test:
updated suppression pattern
mysql-test/suite/binlog/t/binlog_unsafe.test:
updated suppression pattern
mysql-test/suite/ndb/r/ndb_binlog_format.result:
updated result file
mysql-test/suite/ndb/t/ndb_binlog_format.test:
updated suppression pattern
mysql-test/suite/perfschema/r/binlog_stmt.result:
updated result file
mysql-test/suite/perfschema/t/binlog_stmt.test:
updated suppression pattern
mysql-test/suite/rpl/r/rpl_begin_commit_rollback.result:
updated result file
mysql-test/suite/rpl/r/rpl_blackhole.result:
updated result file
mysql-test/suite/rpl/r/rpl_concurrency_error.result:
updated result file
mysql-test/suite/rpl/r/rpl_get_lock.result:
updated result file
mysql-test/suite/rpl/r/rpl_insert_id.result:
updated result file
mysql-test/suite/rpl/r/rpl_insert_ignore.result:
updated result file
mysql-test/suite/rpl/r/rpl_misc_functions.result:
updated result file
mysql-test/suite/rpl/r/rpl_mixed_binlog_max_cache_size.result:
updated result file
mysql-test/suite/rpl/r/rpl_mixed_mixing_engines.result:
updated result file
mysql-test/suite/rpl/r/rpl_mysql_upgrade.result:
updated result file
mysql-test/suite/rpl/r/rpl_non_direct_mixed_mixing_engines.result:
updated result file
mysql-test/suite/rpl/r/rpl_non_direct_row_mixing_engines.result:
updated result file
mysql-test/suite/rpl/r/rpl_non_direct_stm_mixing_engines.result:
updated result file
mysql-test/suite/rpl/r/rpl_nondeterministic_functions.result:
updated result file
mysql-test/suite/rpl/r/rpl_read_only.result:
updated result file
mysql-test/suite/rpl/r/rpl_row_binlog_max_cache_size.result:
updated result file
mysql-test/suite/rpl/r/rpl_row_inexist_tbl.result:
updated result file
mysql-test/suite/rpl/r/rpl_row_mixing_engines.result:
updated result file
mysql-test/suite/rpl/r/rpl_slow_query_log.result:
updated result file
mysql-test/suite/rpl/r/rpl_sp.result:
updated result file
mysql-test/suite/rpl/r/rpl_stm_000001.result:
updated result file
mysql-test/suite/rpl/r/rpl_stm_auto_increment_bug33029.result:
updated result file
mysql-test/suite/rpl/r/rpl_stm_binlog_max_cache_size.result:
updated result file
mysql-test/suite/rpl/r/rpl_stm_loadfile.result:
updated result file
mysql-test/suite/rpl/r/rpl_stm_mixing_engines.result:
updated result file
mysql-test/suite/rpl/r/rpl_stm_start_stop_slave.result:
updated result file
mysql-test/suite/rpl/r/rpl_stm_stop_middle_group.result:
updated result file
mysql-test/suite/rpl/r/rpl_temp_temporary.result:
updated result file
mysql-test/suite/rpl/r/rpl_variables_stm.result:
updated result file
mysql-test/suite/rpl/t/rpl000013.test:
updated suppression pattern
mysql-test/suite/rpl/t/rpl_begin_commit_rollback.test:
updated suppression pattern
mysql-test/suite/rpl/t/rpl_blackhole.test:
updated suppression pattern
mysql-test/suite/rpl/t/rpl_concurrency_error.test:
updated suppression pattern
mysql-test/suite/rpl/t/rpl_err_ignoredtable.test:
updated suppression pattern
mysql-test/suite/rpl/t/rpl_get_lock.test:
updated suppression pattern
mysql-test/suite/rpl/t/rpl_insert.test:
updated suppression pattern
mysql-test/suite/rpl/t/rpl_insert_id.test:
updated suppression pattern
mysql-test/suite/rpl/t/rpl_insert_ignore.test:
updated suppression pattern
mysql-test/suite/rpl/t/rpl_invoked_features.test:
updated suppression pattern
mysql-test/suite/rpl/t/rpl_misc_functions.test:
updated suppression pattern
mysql-test/suite/rpl/t/rpl_mixed_bit_pk.test:
updated suppression pattern
mysql-test/suite/rpl/t/rpl_mysql_upgrade.test:
updated suppression pattern
mysql-test/suite/rpl/t/rpl_nondeterministic_functions.test:
updated suppression pattern
mysql-test/suite/rpl/t/rpl_optimize.test:
updated suppression pattern
mysql-test/suite/rpl/t/rpl_read_only.test:
updated suppression pattern
mysql-test/suite/rpl/t/rpl_semi_sync.test:
updated suppression pattern
mysql-test/suite/rpl/t/rpl_semi_sync_event.test:
updated suppression pattern
mysql-test/suite/rpl/t/rpl_session_var.test:
updated suppression pattern
mysql-test/suite/rpl/t/rpl_slow_query_log.test:
updated suppression pattern
mysql-test/suite/rpl/t/rpl_sp.test:
updated suppression pattern
mysql-test/suite/rpl/t/rpl_stm_auto_increment_bug33029.test:
updated suppression pattern
mysql-test/suite/rpl/t/rpl_stm_found_rows.test:
updated suppression pattern
mysql-test/suite/rpl/t/rpl_stm_insert_delayed.test:
updated suppression pattern
mysql-test/suite/rpl/t/rpl_stm_loadfile.test:
updated suppression pattern
mysql-test/suite/rpl/t/rpl_temp_table.test:
updated suppression pattern
mysql-test/suite/rpl/t/rpl_temp_temporary.test:
updated suppression pattern
mysql-test/suite/rpl/t/rpl_temporary.test:
updated suppression pattern
mysql-test/suite/rpl/t/rpl_timezone.test:
updated suppression pattern
mysql-test/suite/rpl/t/rpl_trigger.test:
updated suppression pattern
mysql-test/suite/rpl/t/rpl_udf.test:
updated suppression pattern
mysql-test/suite/rpl/t/rpl_user_variables.test:
updated suppression pattern
mysql-test/suite/rpl/t/rpl_variables_stm.test:
updated suppression pattern
mysql-test/suite/rpl/t/rpl_view_multi.test:
updated suppression pattern
mysql-test/suite/rpl_ndb/r/rpl_ndb_binlog_format_errors.result:
updated result file
mysql-test/suite/rpl_ndb/t/rpl_ndb_binlog_format_errors.test:
updated suppression pattern
mysql-test/suite/rpl_ndb/t/rpl_ndb_stm_innodb.test:
updated suppression pattern
mysql-test/suite/sys_vars/t/rpl_init_slave_func.test:
updated suppression pattern
mysql-test/t/archive.test:
updated suppression pattern
mysql-test/t/commit_1innodb.test:
updated suppression pattern
mysql-test/t/create_select_tmp.test:
updated suppression pattern
mysql-test/t/ctype_cp932_binlog_stm.test:
updated suppression pattern
mysql-test/t/lock_sync.test:
updated suppression pattern
mysql-test/t/mysqlbinlog.test:
updated suppression pattern
mysql-test/t/mysqldump.test:
updated suppression pattern
mysql-test/t/sp_trans.test:
updated suppression pattern
sql/log_event.cc:
Clarified error message.
sql/share/errmsg-utf8.txt:
Clarified error messages.
2010-04-28 14:47:49 +02:00
Alexander Nozdrin
21b8741b57
After-merge fixes.
2010-04-28 14:33:53 +04:00
unknown
164ff44754
Bug #51839 mixup of DDL causes slave to stop
...
Stored routine DDL statements use statement-based replication
regardless of the current binlog format. The problem here was
that if a DDL statement failed during metadata lock acquisition
or opening of mysql.proc, the binlog format would not be reset
before returning. So the following DDL or DML statements are
binlogged with a wrong binlog format, which causes the slave
to stop.
The problem can be resolved by grabbing an exclusive MDL lock firstly
instead of clearing the current binlog format. So that the binlog
format will not be affected when the lock grab returns directly with
an error. The same way is taken to open a proc table for update.
mysql-test/suite/rpl/r/rpl_tmp_table_and_DDL.result:
Test Result for bug#51839
mysql-test/suite/rpl/t/rpl_tmp_table_and_DDL.test:
Added test to make sure the binlog format is not changed
after a execution of DDL with a table locked.
sql/sp.cc:
Grab an exclusive MDL lock and open a proc table for update firstly
instead of clearing the current binlog format.
2010-04-28 11:26:47 +08:00
Luis Soares
cdb37d69af
BUG#53101: binlog.binlog_tmp_table fails on sol10 sparc64 max in
...
parallel mode
The failure has nothing to do with parallel, but rather on the
order the tests are executed. In this case, the test
binlog_tmp_table (lets call it test2) was not ensuring that the
binary logs would be reset when it started. Later the test issues
a mysqlbinlog .../master-bin.000002 | mysql ... If the test that
was executed before this one (lets call it test1) had issued a
flush logs, then the file in use in test1 (master-bin.000002)
would not actually match the one that was expected. Eventually,
this would cause the statements logged in test1 to be replayed,
instead of the ones logged in the beginning of test2.
We fix this by:
1. adding RESET MASTER to the beginning of binlog_tmp_table
2. setting dynamically the file to use in binlog_tmp_table
Only #1 was needed, but the two make the tests cases more robust.
2010-04-27 12:25:55 +01:00
Alexander Nozdrin
e642701c32
Manual merge from mysql-trunk.
...
Conflicts:
- mysql-test/suite/rpl/r/rpl_stm_mixing_engines.result
2010-04-27 13:58:21 +04:00
Vasil Dimov
c5ca0da1e8
Merge 3417..3421 from mysql-5.1-innodb
2010-04-27 09:16:45 +03:00
Vasil Dimov
777c194cda
Split the innodb.innodb mysql-test.
...
Extract part of innodb.innodb into innodb.innodb_misc1
This is needed in order to be able to more easily debug this test,
under valgrind, it is too huge.
2010-04-27 09:09:08 +03:00
Marko Mäkelä
bd4a354c29
Add a test case for Bug #52745 .
2010-04-26 14:08:56 +03:00
Marko Mäkelä
063928ba05
row_search_for_mysql(): Never try semi-consistent read in unique searches.
...
They are only useful in table scans. (Bug #52663 )
2010-04-26 13:27:25 +03:00
Alfranio Correia
68598c479b
BUG#53075 SBR: Strange warning around CONNECTION_ID
...
Statements with CONNECTION_ID were forced to be kept in the transactional
cache and by consequence non-transactional changes that were supposed to
be flushed ahead of the transaction were kept in the transactional cache.
This happened because after BUG#51894 any statement whose thd's
thread_specific_used was set was kept in the transactional cache. The idea
was to keep changes on temporary tables in the transactional cache. However,
the thread_specific_used was set not only for statements that accessed
temporary tables but also when the CONNECTION_ID was used.
To fix the problem, we created a new variable to keep track of updates
to temporary tables.
mysql-test/suite/rpl/r/rpl_temp_temporary.result:
Added a test case.
mysql-test/suite/rpl/t/rpl_temp_temporary.test:
Added a test case.
sql/log_event.cc:
Uses the thread_temporary_used to decide if a statement should
be kept in the transactional cache or not.
sql/sql_class.cc:
Sets the thread_temporary_used while calling the decide_logging_format.
sql/sql_class.h:
Defines the thread_temporary_used.
sql/sql_parse.cc:
Resets the thread_temporary_used.
2010-04-26 10:02:29 +01:00
Vasil Dimov
75d28784f8
Fix typo in comment in innodb_bug38231.test
2010-04-23 17:12:56 +03:00
Calvin Sun
44bac2ea9c
mysql-5.1-innodb: add error codes to innodb_bug51920.test
...
kill of active connection yields different error code
depending on platform.
2010-04-22 14:16:14 -05:00
Vasil Dimov
66b4a1e614
Merge r3403..3414 from mysql-5.1-innodb:
...
------------------------------------------------------------
revno: 3414
revision-id: marko.makela@oracle.com-20100422093342-jf9ojlzdqsdebohn
parent: marko.makela@oracle.com-20100421185359-8qaxoa2yyrpzwdd7
committer: Marko M?kel? <marko.makela@oracle.com>
branch nick: 5.1-innodb
timestamp: Thu 2010-04-22 12:33:42 +0300
message:
Correct the definition of DICT_SYS_INDEXES_NAME_FIELD.
When row_merge_drop_temp_indexes() was reworked to drop the indexes
via the data dictionary cache, the code was broken because it would
read the index name from the wrong field.
modified:
storage/innodb_plugin/ChangeLog 2425@16c675df-0fcb-4bc9-8058-dcc011a37293:branches%2Fzip%2FChangeLog
storage/innodb_plugin/dict/dict0boot.c 2@16c675df-0fcb-4bc9-8058-dcc011a37293:trunk%2Fdict%2Fdict0boot.c
storage/innodb_plugin/include/dict0boot.h 2@16c675df-0fcb-4bc9-8058-dcc011a37293:trunk%2Finclude%2Fdict0boot.h
------------------------------------------------------------
revno: 3413
revision-id: marko.makela@oracle.com-20100421185359-8qaxoa2yyrpzwdd7
parent: marko.makela@oracle.com-20100421102723-0i80uezbyu0ekj5d
committer: Marko M?kel? <marko.makela@oracle.com>
branch nick: 5.1-innodb
timestamp: Wed 2010-04-21 21:53:59 +0300
message:
btr_page_split_and_insert(): Avoid an infinite loop. (Bug #52964 )
btr_page_tuple_smaller(): New function, refactored from
btr_page_split_and_insert().
btr_page_get_split_rec(): Renamed from btr_page_get_sure_split_rec().
Note that a NULL return may mean that the tuple is to be inserted into
either the lower or upper page, to be determined by btr_page_tuple_smaller().
btr_page_split_and_insert(): When btr_page_get_split_rec() returns NULL,
invoke btr_page_tuple_smaller() to determine which half-page the tuple
belongs to.
Reviewed by Sunny Bains
modified:
storage/innodb_plugin/ChangeLog 2425@16c675df-0fcb-4bc9-8058-dcc011a37293:branches%2Fzip%2FChangeLog
storage/innodb_plugin/btr/btr0btr.c 2@16c675df-0fcb-4bc9-8058-dcc011a37293:trunk%2Fbtr%2Fbtr0btr.c
------------------------------------------------------------
revno: 3412
revision-id: marko.makela@oracle.com-20100421102723-0i80uezbyu0ekj5d
parent: marko.makela@oracle.com-20100421100029-mji6lmdgvuqh96qq
committer: Marko M?kel? <marko.makela@oracle.com>
branch nick: 5.1-innodb
timestamp: Wed 2010-04-21 13:27:23 +0300
message:
dict_create_index_step(): Be strict about DYNAMIC and COMPRESSED tables.
Bug #50495 is about REDUNDANT and COMPACT tables, after all.
modified:
mysql-test/suite/innodb_plugin/r/innodb-zip.result 2252@16c675df-0fcb-4bc9-8058-dcc011a37293:branches%2Fzip%2Fmysql-test%2Finnodb-zip.result
mysql-test/suite/innodb_plugin/t/innodb-zip.test 2252@16c675df-0fcb-4bc9-8058-dcc011a37293:branches%2Fzip%2Fmysql-test%2Finnodb-zip.test
storage/innodb_plugin/ChangeLog 2425@16c675df-0fcb-4bc9-8058-dcc011a37293:branches%2Fzip%2FChangeLog
storage/innodb_plugin/dict/dict0crea.c 2@16c675df-0fcb-4bc9-8058-dcc011a37293:trunk%2Fdict%2Fdict0crea.c
------------------------------------------------------------
revno: 3411
revision-id: marko.makela@oracle.com-20100421100029-mji6lmdgvuqh96qq
parent: marko.makela@oracle.com-20100421095033-0acvzxb8um8cms0a
committer: Marko M?kel? <marko.makela@oracle.com>
branch nick: 5.1-innodb
timestamp: Wed 2010-04-21 13:00:29 +0300
message:
ha_innobase::add_index(): Only check for duplicate indexes
when the data dictionary is locked.
This fixes a UNIV_DEBUG assertion failure in innodb-index.test.
modified:
storage/innodb_plugin/handler/handler0alter.cc 1845@16c675df-0fcb-4bc9-8058-dcc011a37293:branches%2Fzip%2Fhandler%2Fhandler0alter.cc
------------------------------------------------------------
revno: 3410
revision-id: marko.makela@oracle.com-20100421095033-0acvzxb8um8cms0a
parent: marko.makela@oracle.com-20100421094032-ir4glqk46qvg2ywn
committer: Marko M?kel? <marko.makela@oracle.com>
branch nick: 5.1-innodb
timestamp: Wed 2010-04-21 12:50:33 +0300
message:
dtuple_convert_big_rec(): Store locally any fields whose maximum length
is less than 256 bytes. (Bug #52745 )
Add related comments and debug assertions to the "offsets"
functions in rem0rec.c.
Approved by Sunny Bains
modified:
storage/innodb_plugin/ChangeLog 2425@16c675df-0fcb-4bc9-8058-dcc011a37293:branches%2Fzip%2FChangeLog
storage/innodb_plugin/data/data0data.c 2@16c675df-0fcb-4bc9-8058-dcc011a37293:trunk%2Fdata%2Fdata0data.c
storage/innodb_plugin/rem/rem0rec.c 2@16c675df-0fcb-4bc9-8058-dcc011a37293:trunk%2Frem%2Frem0rec.c
------------------------------------------------------------
revno: 3409
revision-id: marko.makela@oracle.com-20100421094032-ir4glqk46qvg2ywn
parent: marko.makela@oracle.com-20100421091611-uu46iygmv5sizjru
committer: Marko M?kel? <marko.makela@oracle.com>
branch nick: 5.1-innodb
timestamp: Wed 2010-04-21 12:40:32 +0300
message:
Adjust tests for the Bug #50495 fix.
modified:
mysql-test/suite/innodb_plugin/r/innodb-zip.result 2252@16c675df-0fcb-4bc9-8058-dcc011a37293:branches%2Fzip%2Fmysql-test%2Finnodb-zip.result
mysql-test/suite/innodb_plugin/t/innodb-zip.test 2252@16c675df-0fcb-4bc9-8058-dcc011a37293:branches%2Fzip%2Fmysql-test%2Finnodb-zip.test
mysql-test/suite/innodb_plugin/t/innodb_bug36169.test 2418@16c675df-0fcb-4bc9-8058-dcc011a37293:branches%2Fzip%2Fmysql-test%2Finnodb_bug36169.test
------------------------------------------------------------
revno: 3408
revision-id: marko.makela@oracle.com-20100421091611-uu46iygmv5sizjru
parent: marko.makela@oracle.com-20100421063916-h3gwjea7jzjilyww
committer: Marko M?kel? <marko.makela@oracle.com>
branch nick: 5.1-innodb
timestamp: Wed 2010-04-21 12:16:11 +0300
message:
rec_convert_dtuple_to_rec(): Correct the debug check.
The "extern" accessor functions return zero or nonzero, not 0 or 1.
modified:
storage/innodb_plugin/rem/rem0rec.c 2@16c675df-0fcb-4bc9-8058-dcc011a37293:trunk%2Frem%2Frem0rec.c
------------------------------------------------------------
revno: 3407
revision-id: marko.makela@oracle.com-20100421063916-h3gwjea7jzjilyww
parent: marko.makela@oracle.com-20100420201550-cax1xywvlcdshgfg
committer: Marko M?kel? <marko.makela@oracle.com>
branch nick: 5.1-innodb
timestamp: Wed 2010-04-21 09:39:16 +0300
message:
rec_convert_dtuple_to_rec(): Add a debug check.
modified:
storage/innodb_plugin/rem/rem0rec.c 2@16c675df-0fcb-4bc9-8058-dcc011a37293:trunk%2Frem%2Frem0rec.c
------------------------------------------------------------
revno: 3406
revision-id: marko.makela@oracle.com-20100420201550-cax1xywvlcdshgfg
parent: marko.makela@oracle.com-20100420114222-diq7h2hiom9ww6me
committer: Marko Makela <marko.makela@oracle.com>
branch nick: 5.1-innodb
timestamp: Tue 2010-04-20 23:15:50 +0300
message:
btr_cur_optimistic_insert(): Remove unused variable "heap".
modified:
storage/innodb_plugin/btr/btr0cur.c 2@16c675df-0fcb-4bc9-8058-dcc011a37293:trunk%2Fbtr%2Fbtr0cur.c
------------------------------------------------------------
revno: 3405
revision-id: marko.makela@oracle.com-20100420114222-diq7h2hiom9ww6me
parent: marko.makela@oracle.com-20100420082908-tpako8jd4imkh1xb
committer: Marko Makela <marko.makela@oracle.com>
branch nick: 5.1-innodb
timestamp: Tue 2010-04-20 14:42:22 +0300
message:
dict_create_index_step(): Invoke dict_index_add_to_cache()
in strict mode only if innodb_strict_mode is set. (Bug #50495 )
trx_is_strict(): New function, for checking innodb_strict_mode.
modified:
storage/innodb_plugin/ChangeLog 2425@16c675df-0fcb-4bc9-8058-dcc011a37293:branches%2Fzip%2FChangeLog
storage/innodb_plugin/dict/dict0crea.c 2@16c675df-0fcb-4bc9-8058-dcc011a37293:trunk%2Fdict%2Fdict0crea.c
storage/innodb_plugin/handler/ha_innodb.cc 2@16c675df-0fcb-4bc9-8058-dcc011a37293:trunk%2Fhandler%2Fha_innodb.cc
storage/innodb_plugin/include/trx0trx.h 2@16c675df-0fcb-4bc9-8058-dcc011a37293:trunk%2Finclude%2Ftrx0trx.h
------------------------------------------------------------
revno: 3404
revision-id: marko.makela@oracle.com-20100420082908-tpako8jd4imkh1xb
parent: marko.makela@oracle.com-20100419103603-u5pz4qc6hfhx4nua
committer: Marko M?kel? <marko.makela@oracle.com>
branch nick: 5.1-innodb
timestamp: Tue 2010-04-20 11:29:08 +0300
message:
Implement UNIV_BTR_AVOID_COPY, an optimization of page splits.
modified:
storage/innodb_plugin/ChangeLog 2425@16c675df-0fcb-4bc9-8058-dcc011a37293:branches%2Fzip%2FChangeLog
storage/innodb_plugin/btr/btr0btr.c 2@16c675df-0fcb-4bc9-8058-dcc011a37293:trunk%2Fbtr%2Fbtr0btr.c
storage/innodb_plugin/include/univ.i 2@16c675df-0fcb-4bc9-8058-dcc011a37293:trunk%2Finclude%2Funiv.i
------------------------------------------------------------
revno: 3403
revision-id: marko.makela@oracle.com-20100419103603-u5pz4qc6hfhx4nua
parent: marko.makela@oracle.com-20100419094405-fd3xwadullishv07
committer: Marko =?ISO-8859-1?Q?M=E4kel=E4?= <marko.makela@oracle.com>
branch nick: 5.1-innodb
timestamp: Mon 2010-04-19 13:36:03 +0300
message:
Enable UNIV_DEBUG_VALGRIND when HAVE_purify is set.
modified:
storage/innobase/include/univ.i 2@cee13dc7-1704-0410-992b-c9b4543f1246:trunk%2Finclude%2Funiv.i
storage/innodb_plugin/include/univ.i 2@16c675df-0fcb-4bc9-8058-dcc011a37293:trunk%2Finclude%2Funiv.i
2010-04-22 14:24:42 +03:00
Luis Soares
fbe81e3c97
BUG#52868: Wrong handling of NULL value during update, replication out
...
of sync
In RBR, sometimes the table->s->last_null_bit_pos can be zero. This
has impact at the slave when it compares records fetched from the
storage engine against records in the binary log event. If
last_null_bit_pos is zero the slave, while comparing in
log_event.cc:record_compare function, would set all bits in the last
null_byte to 1 (assumed all 8 were unused) . Thence it would loose the
ability to distinguish records that were similar in contents except
for the fact that some field was null in one record, but not in the
other. Ultimately this would cause wrong matches, and in the specific
case depicted in the bug report the same record would be updated
twice, resulting in a lost update.
Additionally, in the record_compare function the slave was setting the
X bit unconditionally. There are cases that the X bit does not exist
in the record header. This could also lead to wrong matches between
records.
We fix both by conditionally resetting the bits: (i) unused null_bits
are set if last_null_bit_pos > 0; (ii) X bit is set if
HA_OPTION_PACK_RECORD is in use.
mysql-test/extra/rpl_tests/rpl_record_compare.test:
Shared part of the test case for MyISAM and InnoDB.
mysql-test/suite/rpl/t/rpl_row_rec_comp_innodb.test:
InnoDB test case.
mysql-test/suite/rpl/t/rpl_row_rec_comp_myisam.test:
MyISAM test case. Added also coverage for Field_bits case.
sql/log_event.cc:
Deployed conditional setting of unused bits at record_compare.
sql/log_event_old.cc:
Same change as in log_event.cc.
2010-04-21 13:47:55 +01:00
Marko Mäkelä
66e1700bed
dict_create_index_step(): Be strict about DYNAMIC and COMPRESSED tables.
...
Bug #50495 is about REDUNDANT and COMPACT tables, after all.
2010-04-21 13:27:23 +03:00