An error occurred fetching the project authors.
- 09 Oct, 2006 1 commit
-
-
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.
-
- 16 Feb, 2006 1 commit
-
-
ingo@mysql.com authored
A wrong cast led to numeric overflow for data files greater than 4GB. The parallel repair assumed end of file after reading the amount of data that the file was bigger than 4GB. It truncated the data file and noted the number of records it found so far in the index file header as the number of rows in the table. Removing the cast fixed the problem. I added some cosmetic changes too. The normal repair worked because it uses a different function to read from the data file.
-
- 23 Sep, 2005 1 commit
-
-
- 13 Jun, 2005 1 commit
-
-
georg@lmy002.wdf.sap.corp authored
-
- 19 May, 2005 1 commit
-
-
jimw@mysql.com authored
-
- 13 May, 2005 1 commit
-
-
jimw@mysql.com authored
which allows a FIFO to be used for the non-binary logs. (Bug #8271)
-
- 08 Mar, 2005 1 commit
-
-
jani@ua141d10.elisa.omakaista.fi authored
Reverted Jim's patch.
-
- 03 Mar, 2005 1 commit
-
-
jimw@mysql.com authored
non-seekable files like FIFOs can be used for logs other than the binlog. (Bug #8271)
-
- 15 Jan, 2005 2 commits
-
-
monty@mysql.com authored
-
monty@mysql.com authored
-
- 23 Aug, 2004 1 commit
-
-
monty@mysql.com authored
Cosmetic cleanups Don't call 'delete_elements' on copy_funcs as this causes elements to be freed twice
-
- 10 Jun, 2004 1 commit
-
-
konstantin@mysql.com authored
some reason wasn't included before. A lot of files cleaned up from #include <assert.h>
-
- 03 Jun, 2004 1 commit
-
-
paul@kite-hub.kitebird.com authored
(Note: This affects only comments, not variable names.)
-
- 01 Apr, 2004 1 commit
-
-
dlenev@jabberwock.localdomain authored
Added two status variables: binlog_cache_use - counts number of transactions that used somehow transaction temporary binary log. binlog_cache_disk_use - counts number of transactions that required disk I/O for storing info in this this binary log.
-
- 25 Mar, 2004 1 commit
-
-
serg@serg.mylan authored
bug#3134
-
- 10 Mar, 2004 1 commit
-
-
monty@mysql.com authored
-
- 02 Feb, 2004 1 commit
-
-
ram@gw.mysql.r18.ru authored
-
- 15 Jan, 2004 1 commit
-
-
jani@rhols221.adsl.netsonic.fi authored
open a file that already existed. The problem was that end_io_cache() was called even if init_io_cache() was not. This affected both OUTFILE and DUMPFILE (both fixed). Sometimes wrongly aligned pointer was freed, sometimes mysqld core dumped. Other problem was that select_dump::send_error removed the dumpfile, even if it was created by an earlier run, or by some other program, if the file permissions just permitted it. Fixed it so that the file will only be deleted, if an error occurred, but the file was created by mysqld just a moment ago, in that thread. On the other hand, select_export did not handle the corresponding garbage file at all. Both fixed. After these fixes, a big part of the select_export::prepare and select_dump::prepare code became identical. Merged the code into a new function called create_file(), which is now called by the two latter functions. Regards, Jani
-
- 21 Nov, 2003 1 commit
-
-
monty@mysql.com authored
Fixed tests for RAID tables Detect uninitialized mutexes on lock and destroy
-
- 19 Aug, 2003 1 commit
-
-
guilhem@mysql.com authored
the first 4 bytes of the relay log. Indeed comments in mysys/mf_iocache.c say we must always use my_b_append for such a cache. This *could* avoid a very rare assertion failure which is: 030524 19:32:38 Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '/ users/gbichot/4.1.1/mysql-test/var/log/slave-relay-bin.000001' position: 4 030524 19:32:38 next log '/users/gbichot/4.1.1/mysql-test/var/log/slave-relay-bin.000002' is currently active mysqld: mf_iocache.c:701: _my_b_seq_read: Assertion `pos_in_file == info->end_of_file' failed. and which seemed to happen always when the SQL thread and/or the I/O thread were at position 4 in a relay log.
-
- 26 Jan, 2003 2 commits
-
-
serg@serg.mysql.com authored
-
serg@serg.mysql.com authored
-
- 29 Nov, 2002 1 commit
-
-
monty@mashka.mysql.fi authored
New (simpler) internal timestamp handling. More debuging to heap tables. Small cleanups to multi-table-delete false -> 0 and true -> 1 (We should use TRUE and FALSE)
-
- 21 Aug, 2002 1 commit
-
-
monty@hundin.mysql.fi authored
More DBUG info for replication Better error messages from replication Fixed bug in replication code when connecting to 'localhost' (time was not released properly) Block ALARM signal on Linux for signal handler thread (Fixes problem with running mysqld with --debug) Removed warning when setting an AUTO_INCREMENT field to NULL
-
- 12 Aug, 2002 1 commit
-
-
monty@hundin.mysql.fi authored
Fixed some windows portability problems and removed some compiler warnings Cleaned up QUOTE() function and fixed bug in \0 and \Z handling.
-
- 08 Aug, 2002 1 commit
-
-
monty@mashka.mysql.fi authored
Lots of code fixes to the replication code (especially the binary logging and index log file handling) Fixed bugs in my last changeset that made MySQL hard to compile. Added mutex around some data that could cause table cache corruptions when using OPTIMIZE TABLE / REPAIR TABLE or automatic repair of MyISAM tables. Added mutex around some data in the slave start/stop code that could cause THD linked list corruptions Extended my_chsize() to allow one to specify a filler character. Extend vio_blocking to return the old state (This made some usage of this function much simpler) Added testing for some functions that they caller have got the required mutexes before calling the function. Use setrlimit() to ensure that we can write core file if one specifies --core-file. Added --slave-compressed-protocol Made 2 the minimum length for ft_min_word_len Added variables foreign_key_checks & unique_checks. Less logging from replication code (if not started with --log-warnings) Changed that SHOW INNODB STATUS requre the SUPER privilege More DBUG statements and a lot of new code comments
-
- 23 Jul, 2002 1 commit
-
-
monty@mashka.mysql.fi authored
Made a some new buffers thread specific and changeable. Resize of key_buffer. AUTO_COMMIT -> AUTOCOMMIT Fixed mutex bug in DROP DATABASE Fixed bug when using auto_increment as second part of a key where first part could include NULL. Split handler->extra() to extra() and extra_opt() to be able to support thread specific buffers. Don't write message to error log when slave reconnects becasue of timeout. Fixed possible update problem when using DELETE/UPDATE on small tables (In some cases we used index even if table scanning would be better) A lot of minior code cleanups
-
- 14 Jul, 2002 1 commit
-
-
serg@sergbook.mysql.com authored
-
- 01 Jul, 2002 1 commit
-
-
monty@hundin.mysql.fi authored
Don't free memory from InnoDB at exit (as this may be done before other threads are finnished)
-
- 30 Jun, 2002 2 commits
-
-
serg@serg.mysql.com authored
-
serg@serg.mysql.com authored
-
- 27 Jun, 2002 1 commit
-
-
monty@hundin.mysql.fi authored
-
- 19 Jun, 2002 1 commit
-
-
serg@serg.mysql.com authored
parallel read access to IO_CACHE
-
- 11 Jun, 2002 1 commit
-
-
monty@mashka.mysql.fi authored
(All commit emails since 4.0.1 checked) This had to be done now, before the 4.1 tree changes to much, to make it easy to propagate bug fixes to the 4.1 tree.
-
- 05 Jun, 2002 1 commit
-
-
monty@hundin.mysql.fi authored
Added missing mutex_unlock to slave replication code.
-
- 02 Apr, 2002 1 commit
-
-
sasha@mysql.sashanet.com authored
DBUG_ macro cleanup buffer boundary cleanup This changeset, although not fully tested, works for me better than anything I've had so far, including what is in the repository. I will push it unless something crashes while I am writing this :-)
-
- 29 Jan, 2002 1 commit
-
-
sasha@mysql.sashanet.com authored
-
- 27 Jan, 2002 1 commit
-
-
sasha@mysql.sashanet.com authored
likely() and unlikely() branch prediction compiler hint macros clean-up of comments
-
- 25 Jan, 2002 1 commit
-
-
sasha@mysql.sashanet.com authored
fixed a couple of bugs with SEQ_READ_APPEND cache rpl000016 still has non-deterministic result, but I am going to commit and push since what I have is now better than what is in the main repository
-
- 20 Jan, 2002 1 commit
-
-
sasha@mysql.sashanet.com authored
first pull, merge,test, and get it to work. The main change is the new replication code - now we have two slave threads SQL thread and I/O thread. I have also re-written a lot of the code to prepare for multi-master implementation. I also documented IO_CACHE quite extensively and to some extend, THD class.
-