- 16 Oct, 2006 1 commit
-
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-5.1-ateam
-
- 11 Oct, 2006 1 commit
-
-
istruewing@chilla.local authored
Added proper casts No test case. myisampack must be tested manually.
-
- 10 Oct, 2006 2 commits
-
-
istruewing@chilla.local authored
Raised STACK_MIN_SIZE for Debian GNU/Linux Sid, Linux kernel 2.6.16, gcc version 3.3.6 (Debian 1:3.3.6-13), libc6-dbg 2.3.6.ds1-4, Pentium4 (x86), BUILD/compile-pentium-debug-max Raised about 100 Bytes above the required minimum.
-
istruewing@chilla.local authored
After merge fix. Renamed 'info' -> 'sort_param'.
-
- 09 Oct, 2006 5 commits
-
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-5.1-bug8283
-
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 3 commits
-
-
svoj@april.(none) authored
into mysql.com:/home/svoj/devel/mysql/engines/mysql-5.1-engines
-
svoj@mysql.com/april.(none) authored
-
svoj@may.pils.ru authored
into may.pils.ru:/home/svoj/devel/bk/mysql-5.1-engines
-
- 06 Oct, 2006 12 commits
-
-
svoj@april.(none) authored
into mysql.com:/home/svoj/devel/mysql/BUG22937/mysql-5.1-engines
-
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@april.(none) authored
into mysql.com:/home/svoj/devel/mysql/BUG21381/mysql-5.1-engines
-
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@april.(none) authored
into mysql.com:/home/svoj/devel/mysql/BUG10974/mysql-5.1-engines
-
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 6 commits
-
-
svoj@mysql.com/april.(none) authored
-
svoj@april.(none) authored
into mysql.com:/home/svoj/devel/mysql/BUG21381/mysql-5.1-engines
-
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.
-
brian@zim.(none) authored
Added license information display to output of plugins schema, and tagged all plugins with GPL flag.
-
- 03 Oct, 2006 10 commits
-
-
acurtis/antony@ltamd64.xiphis.org authored
into xiphis.org:/home/antony/work2/p2-bug22080.3
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.1-new-maint
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.1-new-maint
-
-
kroki/tomash@moonlight.intranet authored
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.1-real-bug21726
-
After merge fix. field.cc: After merge fix
-
svoj@mysql.com/april.(none) authored
Fixed a test case according to fix for bug10974.
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.1-new-maint
-
bar@bar.intranet.mysql.r18.ru authored
-