summaryrefslogtreecommitdiff
path: root/storage/innobase
Commit message (Expand)AuthorAgeFilesLines
* Merge mysql-5.1-innodb from bk-internal into my local treeVasil Dimov2010-05-201-2/+2
|\
| * Bug#53593: Add some instrumentation to improve Valgrind sensitivityMarko Mäkelä2010-05-201-2/+2
* | Merge from mysql-trunk-innodb into mysql-5.1-innodb/storage/innobase:Vasil Dimov2010-05-204-3/+15
|/
* Make UNIV_DEBUG Valgrind friendly in the built-in InnoDB.Marko Mäkelä2010-05-191-13/+10
* Make the InnoDB FOREIGN KEY parser understand multi-statements. (Bug #48024)Marko Mäkelä2010-05-148-29/+58
* Remove unused code.Marko Mäkelä2010-05-141-14/+0
* Add Valgrind diagnostics to track down Bug #38999.Marko Mäkelä2010-05-051-0/+16
* fsp_init_file_page_low(): Zero out the page. (Bug #53306)Marko Mäkelä2010-05-042-11/+1
* Add Valgrind checks to catch uninitialized writes to data files.Marko Mäkelä2010-05-041-0/+3
* recv_sys_init(), recv_sys_empty_hash(): Shrink recv_sys->addr_hash.Marko Makela2010-04-291-2/+2
* Reduce the next-key locking of READ UNCOMMITTED to match that ofMarko Makela2010-04-294-18/+18
* Merge r6103 from InnoDB Plugin to the built-in InnoDB to fix Bug #53202:Marko Makela2010-04-284-9/+31
* Do not define UNIV_DEBUG_VALGRIND when HAVE_purify becauseVasil Dimov2010-04-271-0/+6
* lock_rec_queue_validate(): Disable a bogus check thatMarko Mäkelä2010-04-261-2/+23
* row_search_for_mysql(): Never try semi-consistent read in unique searches.Marko Mäkelä2010-04-261-0/+1
* Enable UNIV_DEBUG_VALGRIND when HAVE_purify is set.Marko =?ISO-8859-1?Q?M=E4kel=E4?=2010-04-191-0/+3
* Merge from innodb-branches-5.1Vasil Dimov2010-04-071-1/+1
* Rename the newly added mysql-tests from InnoDB to their proper location.Vasil Dimov2010-03-312-51/+0
* Merge from innodb-branches-5.1Vasil Dimov2010-03-313-5/+58
* Move ./storage/innobase/mysql-test/* into ./mysql-test/* exceptVasil Dimov2010-03-3149-9097/+0
* Import branches/5.1@r6912 from SVN on top of storage/innobaseVasil Dimov2010-03-3154-18/+9153
* Applying InnoDB snapshot, fixes BUG#50691Sergey Vojtovich2010-02-261-1/+9
* Applying InnoDB snapshot, fixes BUG#38901Sergey Vojtovich2010-02-263-14/+35
* Applying InnoDB snapshot, fixes BUG#49001Sergey Vojtovich2010-02-261-32/+60
* Applying InnoDB snapshot Sergey Vojtovich2010-02-261-6/+10
* Applying InnoDB snapshot Sergey Vojtovich2010-02-261-20/+34
* Applying InnoDB snapshot Sergey Vojtovich2010-02-261-34/+20
* Applying InnoDB snapshot Sergey Vojtovich2010-02-261-10/+28
* Applying InnoDB snapshot, fixes BUG#46193.Sergey Vojtovich2010-01-222-103/+131
* Applying InnoDB snapshot Sergey Vojtovich2010-01-222-5/+5
* Applying InnoDB snapshot, fixes BUG#49238.Sergey Vojtovich2010-01-221-9/+23
* Applying InnoDB snapshot 5.1-ss6344, Fixes BUG#47814Satya B2009-12-237-60/+193
* Applying InnoDB snapshot 5.1-ss6344, part 2. Fixes BUG#41609 but doesSatya B2009-12-214-21/+31
* Bug #38883: thd_security_context is not thread safe, crashes?Gleb Shchepa2009-12-031-6/+0
* Bug #38883 (reopened): thd_security_context is not thread safe, crashes?Gleb Shchepa2009-12-014-68/+2
* Applying InnoDB snapshot 5.1-ss6242, part 8. Fixes BUG#47720Satya B2009-11-301-12/+17
* Applying InnoDB snapshot 5.1-ss6242, part 7. Fixes BUG#49032Satya B2009-11-303-11/+30
* Applying InnoDB snapshot 5.1-ss6242, part 5. Fixes BUG#45961Satya B2009-11-301-0/+24
* Applying InnoDB snapshot 5.1-ss6242, part 4. Fixes BUG#48526Satya B2009-11-301-0/+16
* Applying InnoDB snapshot 5.1-ss6242, part 3. Fixes BUG#48469Satya B2009-11-301-2/+9
* Applying InnoDB snapshot 5.1-ss6242, part 2. Fixes BUG#3139Satya B2009-11-302-1/+55
* Applying InnoDB snapshot 5.1-ss6242, part 1. Fixes BUG#32430Satya B2009-11-303-81/+153
* Applying InnoDB snashot 5.1-ss6129Sergey Vojtovich2009-11-021-2/+2
* Applying InnoDB snashot 5.1-ss6129Sergey Vojtovich2009-11-021-2/+2
* Applying InnoDB snashot 5.1-ss6129Sergey Vojtovich2009-11-021-1/+1
* Applying InnoDB snashot 5.1-ss6129Sergey Vojtovich2009-11-021-0/+1
* Applying InnoDB snashot 5.1-ss6129Sergey Vojtovich2009-11-021-2/+2
* Applying InnoDB snashot 5.1-ss6129Sergey Vojtovich2009-11-021-1/+1
* Applying InnoDB snashot 5.1-ss6129Sergey Vojtovich2009-11-021-10/+16
* Applying InnoDB snashot 5.1-ss6129Sergey Vojtovich2009-11-021-1/+3