- 28 Oct, 2014 2 commits
-
-
Igor Babaev authored
-
Igor Babaev authored
Field::selectivity should be set for all fields used in range conditions.
-
- 27 Oct, 2014 2 commits
-
-
Jan Lindström authored
Fix failure seen on dict_foreign_remove_partial().
-
Jan Lindström authored
-
- 26 Oct, 2014 2 commits
-
-
Jan Lindström authored
Merged Facebook commit ec1aac68c74f3c1e558d057c4c9fcfe6edbbea93 authored by Steaphan Greene from https://github.com/facebook/mysql-5.6 In C++11, "" is not parsed as before. So "A""B" is not the same as "AB". Instead, whitespace is required, like: "A" "B"
-
Jan Lindström authored
Merged Facebook commit dd2d11be7aaf3be270e740fb95cbc4eacb52f4d7 authored by Rongrong Zhong from https://github.com/facebook/mysql-5.6 This fixes MySQL Bug #68220 innodb_rows_updated is misleading on slave http://bugs.mysql.com/bug.php?id=68220 Added innodb_system_rows_read/inserted/updated/deleted counters that are the equivalent of innodb_rows_* but that only account for changes made to system databases (mysql, information_schame and preformance_schema). These counters will be used on slaves to differentiated the updates made on system databases from those made on user databases. innodb_rows_* status counters are not updated when innodb_system_rows_* are updated. https://github.com/facebook/mysql-5.6/commit/dd2d11be7aaf3be270e740fb95cbc4eacb52f4d7
-
- 25 Oct, 2014 2 commits
-
-
Jan Lindström authored
Merged Facebook commit ecff018632c6db49bad73d9233c3cdc9f41430e9 authored by Steaphan Greene from https://github.com/facebook/mysql-5.6 This change is to fix: http://bugs.mysql.com/62534 This makes innodb_max_dirty_pages_pct a double with min,default,max values 0.001, 75, 99.999. This also makes innodb_max_dirty_pages_pct_lwm and adaptive_flushing_lwm doubles, as these sysvars are inter-dependent. Added more to the BUFFER POOL AND MEMORY section of SHOW INNODB STATUS: Percent pages dirty: X.X This is all n_dirty_pages / used_pages Percent all pages dirty: X.X This is all n_dirty_pages / all-pages Max dirty pages percent: X.X This is innodb_max_dirty_pages_pct Also changed all of buf from 2 to 3 digits of precision (%.2f -> %.3f).
-
Jan Lindström authored
Merge Facebook commit f981a51a47519b0ba527917887f8adc6df9ae147 authored by Steaphan Greene from https://github.com/facebook/mysql-5.6. This just moves some structure definitions from inside a single .cc file to a shared .h file, with a few tweaks to allow these structures to be shared. On its own, it should have no actual effect. This is needed later.
-
- 24 Oct, 2014 6 commits
-
-
Jan Lindström authored
Merge Facebook commit 25295d003cb0c17aa8fb756523923c77250b3294 authored by Steaphan Greene from https://github.com/facebook/mysql-5.6 This adds a pointer to the trx to each mtr. This allows the trx to be accessed in parts of the code where it was otherwise not available. This is needed later.
-
Jan Lindström authored
compressed pages buf_flush_LRU() returns the number of pages processed. There are two types of processing that can happen. A page can get evicted or a page can get flushed. These two numbers are quite distinct and should not be mixed.
-
Jan Lindström authored
Merge Facebook commit 926a077b14b73c14094de7fc7aa913241b801b4d authored by Inaam Rana from https://github.com/facebook/mysql-5.6. This is fix for upstream bugs http://bugs.mysql.com/bug.php?id=71988 http://bugs.mysql.com/bug.php?id=70500 page_cleaner should work whether or not there is server activity. Its iterations become a noop when there is no work to do but we should not tie it to the server activity. The page_cleaner thread does spurious background flushing because of conditional sleep between iterations. The solution is not to make sleep dependent on server activity etc.
-
Jan Lindström authored
Merged Facebooks commit 6e06bbfa315ffb97d713dd6e672d6054036ddc21 authored by Inaam Rana from https://github.com/facebook/mysql-5.6. Fixes MySQL bug http://bugs.mysql.com/bug.php?id=72123 lock_timeout thread works in a tight loop waking up every second and checking for lock_wait_timeout. In addition, when a mysql thread is forced to wait on a lock, it signals the lock_timeout thread as well. This call is not required. In a heavily contended workload each thread going to wait will signal the lock_timeout thread making it work all the time. As lock_timeout thread scans the array of waiting threads under lock_sys::wait_mutex which is already very hot in contneded loads, these extra scans can cause significanct performance regression. Also, in various codepaths lock_timeout thread is signalled where actual intention was to signal the innodb monitor thread.
-
Jan Lindström authored
Merged Facebook commit bdab302a7e3c37da21a1bffe1550cdbe6c906695 by Inaam Rana from https://github.com/facebook/mysql-5.6. In os_event_wait_time_low() the logic to calculate abs_time for wait is broken. The bug has been present at least since 5.5. It gets acutely sensitized when sub-second wait intervals are passed. It is particularly relevant to us because the page_cleaner thread will mostly request sub-second wait intervals. This can potentially lead to a near tight loop behaviour of page_cleaner with much less sleep then what we'd actually expect.
-
Sergey Vojtovich authored
-
- 23 Oct, 2014 2 commits
-
-
Kentoku SHIBA authored
-
Sergey Petrunya authored
-
- 22 Oct, 2014 2 commits
-
-
Kentoku SHIBA authored
-
Sergey Vojtovich authored
-
- 21 Oct, 2014 3 commits
-
-
Kentoku SHIBA authored
-
Sergey Vojtovich authored
-
Sergey Vojtovich authored
-
- 20 Oct, 2014 5 commits
-
-
Sergey Petrunya authored
-
Kentoku SHIBA authored
-
Sergey Petrunya authored
(Attempt #2) - Don't attempt to use BKA for materialized derived tables. The table is neither filled nor fully opened yet, so attempt to call handler->multi_range_read_info() causes crash.
-
Kentoku SHIBA authored
-
Alexander Barkov authored
-
- 16 Oct, 2014 2 commits
-
-
Sergey Petrunya authored
- Don't attempt to use BKA for materialized derived tables. The table is neither filled nor fully opened yet, so attempt to call handler->multi_range_read_info() causes crash.
-
Sergey Petrunya authored
- Make Mrr_ordered_index_reader::resume_read() restore index position only if it was saved before with Mrr_ordered_index_reader::interrupt_read().
-
- 13 Oct, 2014 1 commit
-
-
Alexander Barkov authored
-
- 12 Oct, 2014 2 commits
-
-
Olivier Bertrand authored
modified: storage/connect/tabodbc.cpp
-
Olivier Bertrand authored
modified: storage/connect/ha_connect.cc storage/connect/plgdbutl.cpp storage/connect/value.cpp storage/connect/value.h
-
- 11 Oct, 2014 2 commits
-
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
- 10 Oct, 2014 5 commits
-
-
Sergey Petrunya authored
- calculate_cond_selectivity_for_table() should handle the case where index statistics is not available (zeros are returned in rec_per_key)
-
Sergei Golubchik authored
-
Olivier Bertrand authored
Was added to ha_connect::GetBooleanOption (otherwise ignored) modified: storage/connect/ha_connect.cc
-
Alexander Barkov authored
-
Alexander Barkov authored
-
- 09 Oct, 2014 2 commits
-
-
Olivier Bertrand authored
terminated string. modified: storage/connect/ha_connect.cc - The Accept and Header Boolean variables were wrongly retrieved using GetIntInfo instead of GetBoolInfo causing some setting to ignored. modified: storage/connect/tabdos.cpp storage/connect/tabdos.h storage/connect/tabfmt.cpp - Fix date truncated because their Value class was not using their field length. modified: storage/connect/ha_connect.cc
-
Sergei Golubchik authored
-