- 17 Jul, 2007 2 commits
-
-
tnurnberg@sin.intern.azundris.com authored
into sin.intern.azundris.com:/home/tnurnberg/27198/51-27198
-
tnurnberg@sin.intern.azundris.com authored
into sin.intern.azundris.com:/home/tnurnberg/27198/50-27198
-
- 16 Jul, 2007 1 commit
-
-
tnurnberg@sin.intern.azundris.com authored
into sin.intern.azundris.com:/home/tnurnberg/27198/41-27198
-
- 13 Jul, 2007 9 commits
-
-
tnurnberg@sin.intern.azundris.com authored
gettimeofday() can fail and presumably, so can time(). Keep an eye on it. Since we have no data on this at all so far, we just retry on failure (and log the event), assuming that this is just an intermittant failure. This might of course hang the threat until we succeed. Once we know more about these failures, an appropriate more clever scheme may be picked (only try so many times per thread, etc., if that fails, return last "good" time() we got or some such). Using sql_print_information() to log as this probably only occurs in high load scenarios where the debug- trace likely is disabled (or might interfere with testing the effect). No test-case as this is a non-deterministic issue.
-
dkatz@damien-katzs-computer.local authored
into damien-katzs-computer.local:/Users/dkatz/mysql51
-
dkatz@damien-katzs-computer.local authored
When opening a new connecgtion, changed mysqltest to prefer a brand new connection slot over an existing, closed slot. Fixes a problem with reused slots that can cause tests to fail. bug#29579
-
dkatz@damien-katzs-computer.local authored
into damien-katzs-computer.local:/Users/dkatz/mysql51
-
dkatz@damien-katzs-computer.local authored
-
dkatz@damien-katzs-computer.local authored
into damien-katzs-computer.local:/Users/dkatz/mysql51
-
dkatz@damien-katzs-computer.local authored
into damien-katzs-computer.local:/Users/dkatz/50
-
dkatz@damien-katzs-computer.local authored
into damien-katzs-computer.local:/Users/dkatz/mysql51
-
dkatz@damien-katzs-computer.local authored
Added an option to yassl to allow "quiet shutdown" like openssl does. This option causes the SSL libs to NOT perform the close_notify handshake during shutdown. This fixes a hang we experience because we hold a lock during socket shutdown.
-
- 11 Jul, 2007 5 commits
-
-
kaa@polly.local authored
into polly.local:/home/kaa/src/maint/mysql-5.0-maint
-
kaa@polly.local authored
into polly.local:/home/kaa/src/maint/mysql-5.1-maint
-
kaa@polly.local authored
into polly.local:/home/kaa/src/maint/bug24192/my51-bug24192
-
kaa@polly.local authored
In case of out-of-memory error received from the master, print the corresponding message to the error log and stop slave I/O thread to avoid reconnecting with a wrong binary log position.
-
Streamlining test for RBR
-
- 10 Jul, 2007 14 commits
-
-
dkatz@damien-katzs-computer.local authored
into damien-katzs-computer.local:/Users/dkatz/mysql51
-
tnurnberg@sin.intern.azundris.com authored
into mysql.com:/home/tnurnberg/22540/51-22540
-
tnurnberg@sin.intern.azundris.com authored
into mysql.com:/home/tnurnberg/22540/51-22540
-
tnurnberg@sin.intern.azundris.com authored
into mysql.com:/home/tnurnberg/22540/50-22540
-
streamlining the test
-
tnurnberg@sin.intern.azundris.com authored
into mysql.com:/home/tnurnberg/22540/51-22540
-
tsmith@sita.local authored
into sita.local:/Users/tsmith/m/bk/maint/51
-
tsmith@sita.local authored
Apply innodb-5.0-* snapshots: ss1489 and ss1547. Fixes: Bug#9709: InnoDB inconsistensy causes "Operating System Error 32/33" Bug#22819: SHOW INNODB STATUS crashes the server with an assertion failure under high load Bug#25645: Assertion failure in file srv0srv.c Bug#27294: insert into ... select ... causes crash with innodb_locks_unsafe_for_binlog=1 Bug#28138: indexing column prefixes produces corruption in InnoDB
-
tsmith@sita.local authored
into sita.local:/Users/tsmith/m/bk/maint/51
-
tsmith@sita.local authored
After applying the snapshots, ensure that code conforms to the final version of WL 3914. It is signficant that, after these changes, InnoDB does not define MYSQL_SERVER, and can be built as an independent storage engine plugin. Fixes: Bug#9709: InnoDB inconsistensy causes "Operating System Error 32/33" Bug#18828: If InnoDB runs out of undo slots, it returns misleading 'table is full' Bug#20090: InnoDB: Error: trying to declare trx to enter InnoDB Bug#20352: Make ibuf_contract_for_n_pages tunable Bug#21101: Wrong error on exceeding max row size for InnoDB table Bug#21293: Deadlock detection prefers to kill long running FOR UPDATE queries Bug#22819: SHOW INNODB STATUS crashes the server with an assertion failure under high load Bug#25078: Make the replication thread to ignore innodb_thread_concurrency Bug#25645: Assertion failure in file srv0srv.c Bug#28138: indexing column prefixes produces corruption in InnoDB
-
ramil/ram@ramil.myoffice.izhnet.ru authored
into mysql.com:/home/ram/work/mysql-5.1-maint
-
Problem: we don't take into account the length of the data written to the temporary data file during update on a CSV table. Fix: properly calculate the data file length during update.
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-new-maint
-
tomas@whalegate.ndb.mysql.com authored
- correct result files
-
- 09 Jul, 2007 9 commits
-
-
tsmith@sita.local authored
Dont touch & chmod the err_log file if using syslog (mysqld_safe)
-
tsmith@sita.local authored
into sita.local:/Users/tsmith/m/bk/maint/51
-
tsmith@sita.local authored
into sita.local:/Users/tsmith/m/bk/maint/50
-
tsmith@sita.local authored
Fix a few typos in comments (from Paul DuBois)
-
tsmith@sita.local authored
into sita.local:/Users/tsmith/m/bk/maint/51
-
tsmith@sita.local authored
Backport from 5.1 a fix to make this test deterministic
-
tsmith@sita.local authored
into sita.local:/Users/tsmith/m/bk/maint/51
-
tsmith@sita.local authored
into sita.local:/Users/tsmith/m/bk/maint/51
-
tsmith@sita.local authored
into sita.local:/Users/tsmith/m/bk/maint/50
-