- 15 Oct, 2016 1 commit
-
-
Sergei Petrunia authored
(why are table reads/writes/updates collected in ha_statistics? this structure was intended for table statistics that the engine reports.. and now it is also used for engine-agnostic statistics like rows_read, rows_requested, etc?)
-
- 10 Oct, 2016 1 commit
-
-
Sergei Petrunia authored
Flashcache is available only in WebScaleSQL (not in MySQL or MariaDB).
-
- 09 Oct, 2016 15 commits
-
-
Sergei Petrunia authored
-
Sergei Petrunia authored
-
Sergei Petrunia authored
-
Sergei Petrunia authored
They have been replaced with increment_statistics() calls made by handler::ha_XXX() methods.
-
Sergei Petrunia authored
-
Sergei Petrunia authored
Issue #108: Index-only scans do not work for partitioned tables and extended keys c1f1f0b64eaecd132fc6ec21663faf0510afacaf
-
Sergei Petrunia authored
-
Sergei Petrunia authored
Leave the code in, but #ifdef it away to avoid compilation error
-
Sergei Petrunia authored
-
Sergei Petrunia authored
Rdb_atomic_perf_counters uses my_io_perf_atomic_struct which uses atomic_stat from include/atomic_stat.h which was backported in the previous cset.
-
Sergei Petrunia authored
commit b5fda565d4bad66f3b5a6432236b96743ccfd323 Author: Steaphan Greene <steaphan@fb.com> Date: Fri Feb 7 21:34:04 2014 -0800 Add basic atomic_stats type Summary: WebScaleSQL Feature: Basic Stats Support This is a simple class template that implements an atomic stats variable. The focus is on performance, not accuracy. No set operations are guaranteed. The other operations are all atomic, so values should not actually be lost - however, there is no attempt to be consistent in reading multiple stats, nor any concern that different threads see any consistent view across multiple stats. Test Plan: This has been tested quite a bit in isolation, and no problems have been found. However, this has never been used in production. Also, a newer, more sophisticated, version of this is already in development. It also shows a small perf gain in the larger stats diffs (Table Stats, User Stats, etc...), when compared to the built-in MySQL atomics. Reviewers: pivanof Reviewed By: pivanof CC: jtolmer, MarkCallaghan, flamingcow, jeremycole, andrew-ford, inaam-rana, liang.guo.752 Differential Revision: https://reviews.facebook.net/D16029 Differential Revision: https://reviews.facebook.net/D16449
-
Sergei Petrunia authored
-
Sergei Petrunia authored
-
Sergei Petrunia authored
-
Sergei Petrunia authored
-
- 07 Oct, 2016 1 commit
-
-
Sergei Petrunia authored
Got to the point where we fail when compiling MyRocks files.
-
- 06 Oct, 2016 4 commits
-
-
Sergei Petrunia authored
-
Sergei Petrunia authored
-
Sergei Petrunia authored
copy of commit 86587affafe77ef555f7c3839839de44f0f203f3 Author: Tian Xia <tianx@fb.com> Date: Tue Oct 4 10:01:52 2016 -0700 Allow filtering of show commands through admission control
-
Georg Richter authored
bash char substitution is not supported for other file options (e.g. read default file)
-
- 04 Oct, 2016 7 commits
-
-
Monty authored
- Fixed compiler warnings - Removed have_debug.inc from innochecksum_3 - Fixed race condition in innodb_buffer_pool_load - Fixed merge issue in innodb-bad-key-change.test - Fixed missing array allocation that could cause function_defaults_notembedded to fail - Fixed thread_cache_size_func
-
Monty authored
Fixed a few failing tests
-
Monty authored
-
Monty authored
This fixed several cases where we where using just ulong for sql_mode
-
Monty authored
This is similar to MysQL Worklog 3253, but with a different implementation. The disk format and SQL syntax is identical with MySQL 5.7. Fetures supported: - "Any" ammount of any trigger - Supports FOLLOWS and PRECEDES to be able to put triggers in a certain execution order. Implementation details: - Class Trigger added to hold information about a trigger. Before this trigger information was stored in a set of lists in Table_triggers_list and in Table_triggers_list::bodies - Each Trigger has a next field that poinst to the next Trigger with the same action and time. - When accessing a trigger, we now always access all linked triggers - The list are now only used to load and save trigger files. - MySQL trigger test case (trigger_wl3253) added and we execute these identically. - Even more gracefully handling of wrong trigger files than before. This is useful if a trigger file uses functions or syntax not provided by the server. - Each trigger now has a "Created" field that shows when the trigger was created, with 2 decimals. Other comments: - Many of the changes in test files was done because of the new "Created" field in the trigger file. This shows up in SHOW ... TRIGGER and when using information_schema.trigger. - Don't check if all memory is released if on uses --gdb; This is needed to be able to get a list from safemalloc of not freed memory while debugging. - Added option to trim_whitespace() to know how many prefix characters was skipped. - Changed a few ulonglong sql_mode to sql_mode_t, to find some wrong usage of sql_mode.
-
Sergei Golubchik authored
-
Daniel Black authored
Signed-off-by: Daniel Black <daniel.black@au.ibm.com>
-
- 03 Oct, 2016 5 commits
-
-
Jan Lindström authored
index creation for SPATIAL indexes.
-
Jan Lindström authored
-
Jan Lindström authored
-
Jan Lindström authored
-
Jan Lindström authored
-
- 01 Oct, 2016 5 commits
-
-
Igor Babaev authored
The bug was caused by a misplaced construct opt_with_clause for one of the variants of CREATE ... SELECT.
-
Igor Babaev authored
-
Igor Babaev authored
The code for st_select_lex::find_table_def_in_with_clauses() did not take into account the fact that the specs for mergeable CTEs were cloned and were not processed by the function With_element::check_dependencies_in_spec().
-
Igor Babaev authored
There was no implementation of the virtual method print() for the Item_window_func class. As a result for a view containing window function an invalid view definition could be written in the frm file. When a query that refers to this view was executed a syntax error was reported.
-
Igor Babaev authored
-
- 30 Sep, 2016 1 commit
-
-
Jan Lindström authored
MDEV-10908: innodb_zip.bug56680 fails in buildbot with InnoDB: Failing assertion: bpage->id.space() == page_id.space() Incorrect merge introduced too strict assertion.
-