An error occurred fetching the project authors.
- 18 Nov, 2009 1 commit
-
-
Sven Sandberg authored
Problem: Some system functions that could return different values on master and slave were not marked unsafe. In particular: GET_LOCK IS_FREE_LOCK IS_USED_LOCK MASTER_POS_WAIT RELEASE_LOCK SLEEP SYSDATE VERSION Fix: Mark these functions unsafe.
-
- 03 Nov, 2009 1 commit
-
-
Alfranio Correia authored
Non-transactional updates that take place inside a transaction present problems for logging because they are visible to other clients before the transaction is committed, and they are not rolled back even if the transaction is rolled back. It is not always possible to log correctly in statement format when both transactional and non-transactional tables are used in the same transaction. In the current patch, we ensure that such scenario is completely safe under the ROW and MIXED modes.
-
- 29 Sep, 2009 1 commit
-
-
Andrei Elkin authored
backporting from 6.0 code base to 5.1.
-
- 03 Oct, 2008 1 commit
-
-
Andrei Elkin authored
The test failed originally -- did not reset binlogging - for the reason identified by bug@15580. However it never can be run on the embedded platfrom for yet another cause - the embedded can not KILL query. Comments added to the test particularly relating `reset master' to the mentioned bug.
-
- 08 Feb, 2008 1 commit
-
-
sven@riska.(none) authored
Problem: mysqlbinlog does not free memory if an error happens. Fix: binlog-processing functions do not call exit() anymore. Instead, they print an error and return an error code. Error codes are propagated all the way back to main, and all allocated memory is freed on the way.
-
- 12 Dec, 2007 1 commit
-
-
msvensson@pilot.mysql.com authored
- dynamic configuration support - safe process - cleanups - create new suite for fedarated
-
- 06 Nov, 2007 2 commits
-
-
aelkin/elkin@koti.dsl.inet.fi authored
non-deterministic tests refining. This particular patch tested on two archs.
-
aelkin/elkin@koti.dsl.inet.fi authored
non-deterministic tests execution on some platforms.
-
- 05 Nov, 2007 1 commit
-
-
aelkin/elkin@koti.dsl.inet.fi authored
refining tests as they appear to be non-deterministic.
-
- 31 Oct, 2007 1 commit
-
-
aelkin/elkin@koti.dsl.inet.fi authored
destination. Removing wrong (local temp) tests.
-
- 27 Jun, 2007 1 commit
-
-
msvensson@pilot.(none) authored
- Update mysql-test-run.pl to collect tests from several suites - Group test into suites - Add suite.opt file
-
- 07 Jun, 2007 1 commit
-
-
msvensson@pilot.(none) authored
Mark one more test as needing binlog
-
- 30 May, 2007 4 commits
-
-
refining the test because of Bug #28786 'reset master' does not reset binlogging on embeded server
-
the test is not supposed for row format. the include-guard is set.
-
merge 5.0 with 5.1
-
test comments correction
-
- 29 May, 2007 4 commits
-
-
combining the final result variable in such way that either option of the test execution will yield zero.
-
tests refining, see binlog_killed.test file for details
-
refining the test.
-
Refining the tests since pb revealed the older version's fragality - the error from SF() due to killed may be different on different env:s. DBUG_ASSERT instead of assert.
-
- 28 May, 2007 1 commit
-
-
The reason for the bug was that replaying of a query on slave could not be possible since its event was recorded with the killed error. Due to the specific of handling INSERT, which per-row-while-loop is unbreakable to killing, the query on transactional table should have not appeared in binlog unless there was a call to a stored routine that got interrupted with killing (and then there must be an error returned out of the loop). The offered solution added the following rule for binlogging of INSERT that accounts the above specifics: For INSERT on transactional-table if the error was not set the only raised flag is harmless and is ignored via masking out on time of creation of binlog event. For both table types the combination of raised error and KILLED flag indicates that there was potentially partial execution on master and consistency is under the question. In that case the code continues to binlog an event with an appropriate killed error. The fix relies on the specified behaviour of stored routine that must propagate the error to the top level query handling if the thd->killed flag was raised in the routine execution. The patch adds an arg with the default killed-status-unset value to Query_log_event::Query_log_event.
-