- 19 Oct, 2006 1 commit
-
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-5.0-merge
-
- 18 Oct, 2006 1 commit
-
-
into mysql.com:/data0/bk/mysql-5.0-kt
-
- 16 Oct, 2006 3 commits
-
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-5.0-bug12240
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-5.0-bug12240
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-4.1-bug12240
-
- 13 Oct, 2006 2 commits
-
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.0-real
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-4.1-bug9678
-
- 12 Oct, 2006 1 commit
-
-
holyfoot/hf@mysql.com/deer.(none) authored
into mysql.com:/home/hf/mysql-5.0.mrg
-
- 11 Oct, 2006 4 commits
-
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-5.0-bug8283
-
istruewing@chilla.local authored
Examined rows are counted for every join part. The per-join-part counter was incremented over all iterations. The result variable was replaced at the end of every iteration. The final result was the number of examined rows by the join part that ended its execution as the last one. The numbers of other join parts was lost. Now we reset the per-join-part counter before every iteration and add it to the result variable at the end of the iteration. That way we get the sum of all iterations of all join parts. No test case. Testing this needs a look into the slow query log. I don't know of a way to do this portably with the test suite.
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1
-
- 10 Oct, 2006 3 commits
-
-
lars@mysql.com/black.(none) authored
into mysql.com:/home/bk/MERGE/mysql-5.0-merge
-
lars@mysql.com/black.(none) authored
into mysql.com:/home/bk/MERGE/mysql-4.1-merge
-
joerg@trift2. authored
into trift2.:/MySQL/M50/push-5.0
-
- 09 Oct, 2006 4 commits
-
-
istruewing@chilla.local authored
After merge fix. MyISAM version 10.
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-5.0-bug8283
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-4.1-bug8283-one
-
istruewing@chilla.local authored
OPTIMIZE TABLE with myisam_repair_threads > 1 performs a non-quick parallel repair. This means that it does not only rebuild all indexes, but also the data file. Non-quick parallel repair works so that there is one thread per index. The first of the threads rebuilds also the new data file. The problem was that all threads shared the read io cache on the old data file. If there were holes (deleted records) in the table, the first thread skipped them, writing only contiguous, non-deleted records to the new data file. Then it built the new index so that its entries pointed to the correct record positions. But the other threads didn't know the new record positions, but put the positions from the old data file into the index. The new design is so that there is a shared io cache which is filled by the first thread (the data file writer) with the new contiguous records and read by the other threads. Now they know the new record positions. Another problem was that for the parallel repair of compressed tables a common bit_buff and rec_buff was used. I changed it so that thread specific buffers are used for parallel repair. A similar problem existed for checksum calculation. I made this multi-thread safe too.
-
- 08 Oct, 2006 4 commits
-
-
svoj@mysql.com/april.(none) authored
into mysql.com:/home/svoj/devel/mysql/engines/mysql-5.0-engines
-
svoj@mysql.com/april.(none) authored
-
svoj@may.pils.ru authored
into may.pils.ru:/home/svoj/devel/bk/mysql-5.0-engines
-
svoj@may.pils.ru authored
into may.pils.ru:/home/svoj/devel/bk/mysql-4.1-engines
-
- 06 Oct, 2006 8 commits
-
-
svoj@mysql.com/april.(none) authored
into mysql.com:/home/svoj/devel/mysql/BUG22937/mysql-5.0-engines
-
svoj@mysql.com/april.(none) authored
into mysql.com:/home/svoj/devel/mysql/BUG22937/mysql-4.1-engines
-
svoj@mysql.com/april.(none) authored
This is addition to fix for bug21617. Valgrind reports an error when opening merge table that has underlying tables with less indexes than in a merge table itself. Copy at most min(file->keys, table->key_parts) elements from rec_per_key array. This fixes problems when merge table and subtables have different number of keys.
-
svoj@mysql.com/april.(none) authored
into mysql.com:/home/svoj/devel/mysql/BUG21381/mysql-5.0-engines
-
svoj@mysql.com/april.(none) authored
-
svoj@mysql.com/april.(none) authored
-
svoj@mysql.com/april.(none) authored
into mysql.com:/home/svoj/devel/mysql/BUG10974/mysql-5.0-engines
-
svoj@mysql.com/april.(none) authored
-
- 05 Oct, 2006 5 commits
-
-
svoj@mysql.com/april.(none) authored
into mysql.com:/home/svoj/devel/mysql/BUG21381/mysql-5.0-engines
-
svoj@mysql.com/april.(none) authored
into mysql.com:/home/svoj/devel/mysql/BUG21381/mysql-4.1-engines
-
svoj@mysql.com/april.(none) authored
Though this is not storage engine specific problem, I was able to repeat this problem with BDB and NDB engines only. That was the reason to add a test case into ndb_update.test. As a result different bad things could happen. BDB has removed duplicate rows which is not expected. NDB returns an error. For multi table update notify storage engine about UPDATE IGNORE as it is done in single table UPDATE.
-
gluh@mysql.com/gluh.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/4.1-kt
-
gluh@mysql.com/gluh.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.0-kt
-
- 03 Oct, 2006 4 commits
-
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0-maint
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.0-real-bug21726-fix-2
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.0-real-bug21726-fix
-
anozdrin/alik@booka. authored
into booka.:/home/alik/MySQL/devel/5.0-rt
-