- 22 Apr, 2005 4 commits
-
-
joreland@mysql.com authored
into mysql.com:/home/jonas/src/mysql-5.0
-
joreland@mysql.com authored
missleading error message
-
joreland@mysql.com authored
-
joreland@mysql.com authored
Redo abort handling according to descr. in Backup.txt bug#9960 - ndb backup increase wait completed timeout to 48 hours
-
- 18 Apr, 2005 3 commits
-
-
joreland@mysql.com authored
4.1->5.0 merge fix
-
joreland@mysql.com authored
into mysql.com:/home/jonas/src/mysql-5.0
-
joreland@mysql.com authored
Make BUILDINDX RF_LOCAL aware
-
- 14 Apr, 2005 6 commits
-
-
joreland@mysql.com authored
into mysql.com:/home/jonas/src/mysql-5.0
-
joreland@mysql.com authored
Crash if ACC_CONTOPREQ was sent while ACC_LCPCONF was in job buffer if ACC_LCPCONF would have arrived eariler (before TUP_LCPSTARTED) operations could lockup. But would be restarted on next LCP -- LQH 1) Better check for LCP started that will also return true if ACC or TUP already has completed 2) Remove incorrect if statement that prevented operations to be started if ACC has completed -- ACC Make sure all ACC_CONTOPCONF are sent before releasing lcp record i.e. use noOfLcpConf == 4 (2 ACC_LCPCONF + 2 ACC_CONTOPCONF) Check for == 4 also when sending ACC_CONTOPCONF
-
joreland@mysql.com authored
into mysql.com:/home/jonas/src/mysql-5.0
-
heikki@hundin.mysql.fi authored
into hundin.mysql.fi:/home/heikki/mysql-5.0
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-5.0-0
-
igor@rurik.mysql.com authored
Added a test in connection with the fix for bug #6106. view.result, view.test: Added test cases for bugs #6106/6107. sql_show.cc: The addition of the case for items of the type REF_ITEM in the function uses_only_table_name_fields became necessary after the fix for bug #6106. sql_base.cc: The problem was due to the fact that two different column references were glued together though one of them belonged to a subquery while another to an outer query. This caused eventually a wrong calculation of values for the used_tables attribute.
-
- 13 Apr, 2005 27 commits
-
-
petr@mysql.com authored
into mysql.com:/home/cps/mysql/trees/mysql-5.0
-
petr@mysql.com authored
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-5.0-clean
-
konstantin@mysql.com authored
-
heikki@hundin.mysql.fi authored
-
jimw@mysql.com authored
-
heikki@hundin.mysql.fi authored
Fix part of bug #9670: if MySQL calls ::store_lock with TL_IGNORE, do not change prebuilt->select_lock_type; this fix may heal the assertion failures reported in UPDATE and multi-table UPDATE; it is not clear if this fixes the problems in OPTIMIZE TABLE
-
mskold@mysql.com authored
into mysql.com:/usr/local/home/marty/MySQL/mysql-5.0
-
jimw@mysql.com authored
-
mskold@mysql.com authored
into mysql.com:/usr/local/home/marty/MySQL/mysql-5.0
-
pem@mysql.com authored
into mysql.com:/home/pem/work/mysql-5.0
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-4.1-clean
-
pem@mysql.comhem.se authored
causes system crash.
-
mskold@mysql.com authored
-
pem@mysql.comhem.se authored
-
mskold@mysql.com authored
-
heikki@hundin.mysql.fi authored
At the shutdown, write the latest lsn only to the first pages of the ibdata files of the system tablespace, NOT to the .ibd files; writing to tens of thousands .ibd files can take minutes
-
pem@mysql.comhem.se authored
-
heikki@hundin.mysql.fi authored
Fix the patch of Jan to optimize next-key locking in searches of type 'primary key >= some value'
-
heikki@hundin.mysql.fi authored
into hundin.mysql.fi:/home/heikki/mysql-4.1
-
heikki@hundin.mysql.fi authored
Do not test the value of err if the lock operation was skipped because innodb_logs_unsafe_for_binlog was TRUE; though this did not cause any bugs visible to the user, because err is inited to DB_SUCCESS at the start of the function row_search_for_mysql()
-
mskold@mysql.com authored
-
mskold@mysql.com authored
-
mskold@mysql.com authored
-
mskold@mysql.com authored
-
jan@hundin.mysql.fi authored
not produce phantom (bug #9354).
-
joreland@mysql.com authored
1) Make getNoParall into function instead of a procedure 2) Check for multiple transactions in "upgrade's" parallell queue 3) Set lock mode according to lock_owner's lockMode NOTE: Does still not handle lock upgrade in case of aborts correctly
-