summaryrefslogtreecommitdiff
path: root/mysql-test/suite
Commit message (Collapse)AuthorAgeFilesLines
* MDEV-26: Global transaction ID.unknown2013-04-042-0/+74
| | | | | | | | | Move combining slave and gtid binlog state into a separate function. Make SHOW ALL SLAVES STATUS use the same function, so it shows the same value used by slave connect. Add a test case.
* MDEV-26: Global transaction IDunknown2013-04-024-35/+13
| | | | | | | | | | | | | More fixes for test failures in Buildbot: - Do not run crashing test in Valgrind. - FLUSH TABLES did not work to avoid errors about not closed tables when crashing server. Suppress the messages instead. - Rewrite multi-source test case to only start one pair of slave threads at a time, to work-around the bug MDEV-4352.
* MDEV-26: Global transaction ID.unknown2013-03-294-4/+33
| | | | More fixes for race conditions in test cases.
* MDEV-26: Global transaction ID.unknown2013-03-292-6/+6
| | | | | | | | | | Fix yet another race in the rpl_gtid_startpos test case. Implement include/wait_for_purge.inc to purge binary logs; we need to retry the purge multiple times until it succeeds in removing all the logs we want, as binlog dump threads can be slow to stop on loaded machines and hold back purge of logs that are still referenced by the thread.
* MDEV-26: Global transaction ID.unknown2013-03-282-0/+165
| | | | | | | | Add tests crashing the slave in the middle of replication and checking that replication picks-up again on restart in a crash-safe way. Fix silly code that causes crash by inserting uninitialised data into a hash.
* MDEV-26: Global transaction ID.unknown2013-03-288-0/+70
| | | | Fix some test case races and .result file updates, found with Buildbot.
* MDEV-26: Global transaction ID.unknown2013-03-272-4/+103
| | | | | | | | | | Test crashing the master, check that it recovers the binlog state. Fix one bug introduced by previous commit (crash-recoved binlog state was overwritten by loading stale binlog state file). Fix Windows build error.
* MDEV-26: Global transaction ID.unknown2013-03-272-0/+155
| | | | | | | | | | | | | | | | Implement test case rpl_gtid_stop_start.test to test normal stop and restart of master and slave mysqld servers. Fix a couple bugs found with the test: - When InnoDB is disabled (no XA), the binlog state was not read when master mysqld starts. - Remove old code that puts a bogus D-S-0 into the initial binlog state, it is not correct in current design. - Fix memory leak in gtid_find_binlog_file().
* MDEV-26: Global transaction ID.unknown2013-03-272-0/+48
| | | | | | | | | | | | | | When slave requested to start at some GTID, and that GTID was the very last event (within its replication domain) in some binlog file, we did not allow the binlog dump thread on the master to start from the beginning of a following binlog file. This is a problem, since the binlog file containing the GTID is likely to be purged if the replication domain is unused for long. With this fix, if the Gtid list event at the start of a binlog file contains exactly the GTID requested by the slave, we allow to start the binlog dump thread from this file, taking care not to skip any events from that domain in the file.
* MDEV-26: Global transaction ID.unknown2013-03-272-0/+47
| | | | Fix bug that RESET SLAVE did not reset Using_Gtid back to 0.
* MDEV-26: Global transaction ID.unknown2013-03-274-0/+67
| | | | | | | | Fix MDEV-4329. When user does CHANGE MASTER TO MASTER_GTID_POS='<explicit GTID state>', we check that this state does not conflict with the binlog. But the code forgot to give an error in the case where a domain was completely missing from the requested position (eg. MASTER_GTID_POS='').
* MDEV-26: Global transaction IDunknown2013-03-26140-8259/+10224
| | | | | | | | | | | Adjust full test suite to work with GTID. Huge patch, mainly due to having to update .result file for all SHOW BINLOG EVENTS and mysqlbinlog outputs, where the new GTID events pop up. Everything was painstakingly checked to be still correct and valid .result file updates.
* MDEV-26: Global transaction ID.unknown2013-03-222-8/+9
| | | | | Fix checksums for the new GTID events (reported by Pavel Ivanov). Fix printing of GTID_LIST_EVENT.
* MDEV-26: Global transaction ID.unknown2013-03-212-8/+56
| | | | | Fix error handling when record_gtid() fails to update the mysql.rpl_slave_state table.
* MDEV-26: Global transaction ID.unknown2013-03-212-0/+39
| | | | | | | Fix MDEV-4278: Slave does not check that master understands GTID. Now the slave will abort with a suitable error if an attempt is made to connect with GTID to a master that does not support GTID.
* MDEV-26: Global transaction ID.unknown2013-03-215-1/+155
| | | | | | | | | | | | | | | Fix MDEV-4275 - I/O thread restart duplicates events in the relay log. The first time we connect to master after CHANGE MASTER or restart, we connect from the GTID position. But then subsequent reconnects or IO thread restarts reconnect with the old-style file/offset binlog pos from where it left off at last disconnect. This is necessary to avoid duplicate events in the relay logs, as there is nothing that synchronises the SQL thread update of GTID state (multiple threads in case of multi-source) with IO thread reconnects. Test cases. Some small cleanups and fixes.
* MDEV-26: Global transaction ID.unknown2013-03-187-0/+291
| | | | | | | | | | | | | Fix things so that a master can switch with MASTER_GTID_POS=AUTO to a slave that was previously running with log_slave_updates=0, by looking into the slave replication state on the master when the slave requests something not present in the binlog. Be a bit more strict about what position the slave can ask for, to avoid some easy-to-hit misconfiguration errors. Start over with seq_no counter when RESET MASTER.
* MDEV-26: Global transaction ID.unknown2013-03-143-15/+15
| | | | | After-rebase fixes. Rebase was done to be able to build on top of the binlog background thread of MDEV-532.
* MDEV-26: Global Transaction ID.unknown2013-03-112-0/+89
| | | | | | | | | Improvements to record_gtid(): - Check for correct table definition of mysql.rpl_slave_state - Use autocommit, to save one call to ha_commit_trans() - Slightly more efficient way to set table->write_set - Use ha_index_read_map() to locate rows to support any storage engine.
* MDEV-26: Global Transaction IDunknown2013-02-272-0/+103
| | | | | | | | Fix that CHANGE MASTER ... MASTER_GTID_POS="" works to start from the very beginning of the binary log (with test case). Fix that not finding the requested GTID position in master binlog results in fatal error, not endless connect retry.
* MDEV-26: Global Transaction ID.unknown2013-02-273-0/+327
| | | | | | | | Add test case demonstrating multi-source replication with GTID. Test that we can move from being slave of two masters to be a slave deeper down in the hierarchy (of a higher-up multi-source slave), and vice versa.
* MDEV-26: Global transaction IDunknown2013-02-212-0/+150
| | | | | | | | | | | | | | - Add first basic mysql-test-run test case which tests switch to new master using MASTER_GTID_POS=AUTO. - When we connect with GTID, do not use any old relay logs, as they may contain the wrong events or be corrupt after crash. - Fix old bug that fails replication if we receive a heartbeat event immediately after an event was omitted in the stream from the master. - Fix rpl_end to clear Gtid_Pos_Auto, to keep check_testcase happy.
* MDEV-26: Global transaction ID.unknown2013-02-183-0/+109
| | | | | | | Fix initial loading of mysql.rpl_slave_state, the code had several issues. Some very basic MTR stuff, more to come.
* Fix buildbot failure:Sergey Petrunya2013-03-074-0/+1327
| | | | | Backport the code that runs cassandra.test only when Cassandra is present and running from 10.0 to 10.0-base.
* Automatic mergeMichael Widenius2013-02-272-0/+43
|\
| * Fixed BUG#51763 Can't delete rows from MEMORY table with HASH keyMichael Widenius2013-02-152-0/+43
| | | | | | | | | | | | | | | | | | | | | | mysql-test/suite/heap/heap.result: Added test case mysql-test/suite/heap/heap.test: Added test case storage/heap/hp_delete.c: Fixed that we don't change order of keys for the current key when we delete them from the hash table. Fixed that 'current_hash_ptr' is correct after heap_delete_key(). Don't "reset current_hash_ptr" on delete; This will improve time a lot for delete of rows when not all rows matches the search criteria.
* | [NOT] EXISTS to IN transformation.unknown2013-02-264-31/+31
|/
* MDEV-3984: Double free of Master_info * when CHANGE MASTER fails.unknown2013-01-302-0/+13
| | | | | | When CHANGE MASTER fails, it may or may not have already added the Master_info * to the index. Implement logic that properly handles removal and freeing in both cases.
* 5.5 mergeSergei Golubchik2013-01-2971-301/+18037
|\
| * Fixed MDEV-3890: Server crash inserting record on a temporary table after ↵Michael Widenius2013-01-252-0/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | truncating it The problem was that a temporary table was re-created as a non-temporary table. mysql-test/suite/maria/truncate.result: Added test cases mysql-test/suite/maria/truncate.test: Added test cases sql/sql_truncate.cc: Mark that table to be created is a temporary table storage/maria/ha_maria.cc: Ensure that temporary tables are not transactional.
| * Merge 5.3->5.5Igor Babaev2013-01-232-0/+30
| |\
| | * Merge 5.2->5.3Igor Babaev2013-01-212-0/+30
| | |\
| | | * Corrected the test case for bug mdev-3938.Igor Babaev2013-01-192-0/+3
| | | |
| | | * Fixed bug mdev-3938.Igor Babaev2013-01-152-0/+28
| | | | | | | | | | | | | | | | | | | | | | | | The original patch with the implementation of virtual columns did not support INSERT DELAYED into tables with virtual columns. This patch fixes the problem.
| * | | remove one particularly stupid test Sergei Golubchik2013-01-232-6/+0
| | | |
| * | | xtradb merge. Percona-Server-5.5.28-rel29.3Sergei Golubchik2013-01-1610-8/+14
| | | |
| * | | Test case and a different fix for MySQL bug#14485479Sergei Golubchik2013-01-152-0/+39
| | | |
| * | | small cleanupsSergei Golubchik2013-01-155-0/+0
| | | |
| * | | mysql-5.5.29 mergeSergei Golubchik2013-01-1516-22/+163
| |\ \ \
| | * \ \ BUG#14659685: main.mysqlbinlog_row_myisam.test ↵Shivji Kumar Jha2012-10-3015-0/+17159
| | |\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | main.mysqlbinlog_row_innodb.test are skipped merge from 5.1 into 5.5
| | * \ \ \ merge from mysql-5.1 -> mysql-5.5Krunal Bauskar krunal.bauskar@oracle.com2012-10-172-0/+148
| | |\ \ \ \
| | * | | | | removing .... will re-add using merge. for some reason initial mysql-5.1 ↵Krunal Bauskar krunal.bauskar@oracle.com2012-10-172-131/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | version is not connected to mysql-5.5
| | * | | | | removed warning message as they have changed in mysql-5.6 and mysql-trunk ↵Krunal Bauskar krunal.bauskar@oracle.com2012-10-152-3/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | and this is left over from changes that got up-merged
| | * | | | | bug#14704286Krunal Bauskar krunal.bauskar@oracle.com2012-10-152-0/+132
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | SECONDARY INDEX UPDATES MAKE CONSISTENT READS DO O(N^2) UNDO PAGE LOOKUPS (honoring kill query while accessing sec_index) If secondary index is being used for select query evaluation and this query is operating with consistent read snapshot it might take good time for secondary index to return back control to mysql as MVCC would kick in. If user issues "kill query <id>" while query is actively accessing secondary index it will not be honored as there is no hook to check for this condition. Added hook for this check. ----- Parallely secondary index taking too long to evaluate for consistent read snapshot case is being examined for performance improvement. WL#6540.
| | * | | | | Bug #14036214 MYSQLD CRASHES WHEN EXECUTING UPDATE IN TRX WITHAnnamalai Gurusami2012-10-082-7/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | CONSISTENT SNAPSHOT OPTION A transaction is started with a consistent snapshot. After the transaction is started new indexes are added to the table. Now when we issue an update statement, the optimizer chooses an index. When the index scan is being initialized via ha_innobase::change_active_index(), InnoDB reports the error code HA_ERR_TABLE_DEF_CHANGED, with message stating that "insufficient history for index". This error message is propagated up to the SQL layer. But the my_error() api is never called. The statement level diagnostics area is not updated with the correct error status (it remains in Diagnostics_area::DA_EMPTY). Hence the following check in the Protocol::end_statement() fails. 516 case Diagnostics_area::DA_EMPTY: 517 default: 518 DBUG_ASSERT(0); 519 error= send_ok(thd->server_status, 0, 0, 0, NULL); 520 break; The fix is to backport the fix of bugs 14365043, 11761652 and 11746399. 14365043 PROTOCOL::END_STATEMENT(): ASSERTION `0' FAILED 11761652 HA_RND_INIT() RESULT CODE NOT CHECKED 11746399 RETURN VALUES OF HA_INDEX_INIT() AND INDEX_INIT() IGNORED rb://1227 approved by guilhem and mattiasj.
| | * | | | | BUG#12604949. Increased timeout for switching sync->async. Number of ↵Serge Kozlov2012-10-022-14/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | iterations for loops sets 10.
| | * | | | | upmerge to bug#14548159Rohit Kalhans2012-09-226-43/+43
| | |\ \ \ \ \
| | * | | | | | Do not try innodb_change_buffering_debug=2.Marko Mäkelä2012-09-202-4/+3
| | | | | | | |
| | * | | | | | Local mergeMarc Alff2012-09-072-0/+24
| | |\ \ \ \ \ \
| | | * | | | | | Bug#14072995 - PERFSCHEMA.FUNC_FILE_IO FAILS WITH RESULT CONTENT MISMATCH ↵Marc Alff2012-09-072-0/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | OCASSIONALLY ON PB2 Improved the robustness of the func_file_io tests.
View Lorry Controller Status