summaryrefslogtreecommitdiff
path: root/storage/tokudb
Commit message (Collapse)AuthorAgeFilesLines
* MDEV-19818 Reuse new I_S table definition helper classes for TokuDBAlexander Barkov2019-06-2117-60/+168
|
* Merge 10.4 into 10.5Marko Mäkelä2019-06-181-6/+2
|\
| * Merge branch '10.3' into 10.4Oleksandr Byelkin2019-06-141-6/+2
| |\
| | * Merge branch '10.2' into 10.3Oleksandr Byelkin2019-06-141-6/+2
| | |\
| | | * Merge 10.1 into 10.2Marko Mäkelä2019-06-121-6/+2
| | | |\
| | | | * MDEV-15734 - calculation inside sizeof() warningSergey Vojtovich2019-05-301-6/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Reverted incorrect change introduced by 548d03d7. As result is char**, third qsort() parameter must be sizeof(char*). Not sizeof(result[0] + 2), which is same as sizeof(result[0]). Not even sizeof(result[0]) + 2, which would cause invalid memory access. Proper sorting is responsibility of logfilenamecompare() callback.
* | | | | MDEV-19710 Split the server side code in rpl_utility.cc into virtual methods ↵Alexander Barkov2019-06-072-2/+2
| | | | | | | | | | | | | | | | | | | | in Type_handler
* | | | | MDEV-17709 Remove handlerton::stateRobert Bindar2019-06-061-1/+0
|/ / / /
* | | | Merge branch '10.3' into 10.4Oleksandr Byelkin2019-05-1925-32/+130
|\ \ \ \ | |/ / /
| * | | Merge 10.2 into 10.3Marko Mäkelä2019-05-1415-19/+19
| |\ \ \ | | |/ /
| | * | Merge 10.1 into 10.2Marko Mäkelä2019-05-1315-19/+19
| | |\ \ | | | |/
| | | * Merge branch '5.5' into 10.1Vicențiu Ciorbaru2019-05-1115-19/+19
| | | |\
| | | | * Update FSF AddressVicențiu Ciorbaru2019-05-111039-1044/+1044
| | | | | | | | | | | | | | | | | | | | * Update wrong zip-code
| * | | | Merge branch '10.2' into 10.3Oleksandr Byelkin2019-05-1210-13/+111
| |\ \ \ \ | | |/ / /
| | * | | Merge branch '10.1' into 10.2Oleksandr Byelkin2019-05-0410-13/+111
| | |\ \ \ | | | |/ /
| | | * | MDEV-19265 Server should throw warning if event is created and ↵Vladislav Vaintroub2019-04-281-0/+2
| | | | | | | | | | | | | | | | | | | | event_scheduler = OFF
| | | * | Merge branch 'merge-tokudb-5.6' into 10.1Sergei Golubchik2019-04-269-13/+109
| | | |\ \
| | | | * | 5.6.43-84.3Sergei Golubchik2019-04-2643-1088/+1888
| | | | | |
* | | | | | remove -fno-rttiSergei Golubchik2019-05-181-1/+0
| | | | | |
* | | | | | Disable 5733_tokudb as the result is not stableMonty2019-05-091-0/+1
| | | | | |
* | | | | | Adjusted result for tokudb_bugs.db756_card_part_hash_2_pickVarun Gupta2019-04-262-0/+7
| | | | | |
* | | | | | Results updated for tokudb testsVarun Gupta2019-04-2529-1/+100
| | | | | |
* | | | | | Merge 10.3 into 10.4Marko Mäkelä2019-04-031-2/+2
|\ \ \ \ \ \ | |/ / / / /
| * | | | | Merge 10.2 into 10.3Marko Mäkelä2019-04-031-2/+2
| |\ \ \ \ \ | | |/ / / /
| | * | | | Merge 10.1 into 10.2Marko Mäkelä2019-04-031-2/+2
| | |\ \ \ \ | | | |/ / /
| | | * | | cmake: only search for libraries that are neededSergei Golubchik2019-04-021-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | in particular, don't search for libjemalloc.a, which is only needed for tokudb's ftcxx tests, when the tests aren't going to be built.
* | | | | | Write information about restart in .resultMichael Widenius2019-04-016-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | Idea comes from MySQL which does something similar
* | | | | | MDEV-371 Unique Index for long columnsSachin2019-02-225-13/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch implements engine independent unique hash index. Usage:- Unique HASH index can be created automatically for blob/varchar/test column whose key length > handler->max_key_length() or it can be explicitly specified. Automatic Creation:- Create TABLE t1 (a blob unique); Explicit Creation:- Create TABLE t1 (a int , unique(a) using HASH); Internal KEY_PART Representations:- Long unique key_info will have 2 representations. (lets understand this with an example create table t1(a blob, b blob , unique(a, b)); ) 1. User Given Representation:- key_info->key_part array will be similar to what user has defined. So in case of example it will have 2 key_parts (a, b) 2. Storage Engine Representation:- In this case there will be only one key_part and it will point to HASH_FIELD. This key_part will be always after user defined key_parts. So:- User Given Representation [a] [b] [hash_key_part] key_info->key_part ----^ Storage Engine Representation [a] [b] [hash_key_part] key_info->key_part ------------^ Table->s->key_info will have User Given Representation, While table->key_info will have Storage Engine Representation.Representation can be changed into each other by calling re/setup_keyinfo_hash function. Working:- 1. So when user specifies HASH_INDEX or key_length is > handler->max_key_length(), In mysql_prepare_create_table One extra vfield is added (for each long unique key). And key_info->algorithm is set to HA_KEY_ALG_LONG_HASH. 2. In init_from_binary_frm_image values for hash_keypart is set (like fieldnr , field and flags) 3. In parse_vcol_defs, HASH_FIELD->vcol_info is created. Item_func_hash is used with list of Item_fields, When Explicit length is given by user then Item_left is used to concatenate Item_field values. 4. In ha_write_row/ha_update_row check_duplicate_long_entry_key is called which will create the hash key from table->record[0] and then call ha_index_read_map , if we found duplicated hash , we will compare the result field by field.
* | | | | | Merge branch '10.3' into 10.4Oleksandr Byelkin2019-02-2134-1069/+1777
|\ \ \ \ \ \ | |/ / / / /
| * | | | | Merge branch '10.3' into bb-10.3-mergeOleksandr Byelkin2019-02-121-0/+2
| |\ \ \ \ \
| | * | | | | Removed compiler warnings from tokudbMonty2019-02-061-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | - Backport from 10.4
| * | | | | | dirty mergeOleksandr Byelkin2019-02-0734-1069/+1777
| |\ \ \ \ \ \ | | |/ / / / / | |/| / / / / | | |/ / / /
| | * | | | Merge 10.1 into 10.2Marko Mäkelä2019-02-0334-1069/+1777
| | |\ \ \ \ | | | |/ / / | | | | | | | | | | | | | | | | | | | | | | | | Temporarily disable a test for commit 2175bfce3e9da8332f10ab0e0286dc93915533a2 because fixing it in 10.2 requires updating libmariadb.
| | | * | | Merge 10.1 into 10.1Marko Mäkelä2019-02-0234-1069/+1777
| | | |\ \ \ | | | | | | | | | | | | | | | | | | | | | This is joint work with Oleksandr Byelkin.
| | | | * | | MariaDB detect incorrect table nameOleksandr Byelkin2019-01-292-2/+3
| | | | | | |
| | | | * | | Fix detection of version in tokudbOleksandr Byelkin2019-01-281-1/+1
| | | | | | |
| | | | * | | Merge branch 'merge-tokudb-5.6' into 10.0Oleksandr Byelkin2019-01-2834-1069/+1776
| | | | |\ \ \
| | | | | * | | 5.6.42-84.2Oleksandr Byelkin2019-01-2435-1075/+1778
| | | | | |/ /
* | | | | | | Merge branch '10.4' into bb-10.4-mdev7486bb-10.4-mdev7486Igor Babaev2019-02-194-4/+4
|\ \ \ \ \ \ \
| * | | | | | | MDEV-17903: New optimizer defaults: change optimize_join_buffer_size to be ONVarun Gupta2019-02-194-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | optimize_join_buffer_size is switched ON.
* | | | | | | | MDEV-7486: Condition pushdown from HAVING into WHEREGalina Shalygina2019-02-174-4/+4
|/ / / / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Condition can be pushed from the HAVING clause into the WHERE clause if it depends only on the fields that are used in the GROUP BY list or depends on the fields that are equal to grouping fields. Aggregate functions can't be pushed down. How the pushdown is performed on the example: SELECT t1.a,MAX(t1.b) FROM t1 GROUP BY t1.a HAVING (t1.a>2) AND (MAX(c)>12); => SELECT t1.a,MAX(t1.b) FROM t1 WHERE (t1.a>2) GROUP BY t1.a HAVING (MAX(c)>12); The implementation scheme: 1. Extract the most restrictive condition cond from the HAVING clause of the select that depends only on the fields that are used in the GROUP BY list of the select (directly or indirectly through equalities) 2. Save cond as a condition that can be pushed into the WHERE clause of the select 3. Remove cond from the HAVING clause if it is possible The optimization is implemented in the function st_select_lex::pushdown_from_having_into_where(). New test file having_cond_pushdown.test is created.
* | | | | | | MDEV-16188 Post merge fixes: more for TokuDBIgor Babaev2019-02-0810-31/+37
| | | | | | |
* | | | | | | MDEV-16188 Post merge fixes fot TokuDBIgor Babaev2019-02-0827-308/+388
| | | | | | |
* | | | | | | Fix test result differencesMarko Mäkelä2019-01-079-0/+608
| | | | | | |
* | | | | | | Merge 10.3 into 10.4Marko Mäkelä2019-01-0612-21/+30
|\ \ \ \ \ \ \ | |/ / / / / /
| * | | | | | Merge branch '10.2' into 10.3Sergei Golubchik2019-01-0312-21/+30
| |\ \ \ \ \ \ | | |/ / / / /
| | * | | | | Merge branch '10.1' into 10.2Sergei Golubchik2019-01-0310-0/+0
| | |\ \ \ \ \ | | | |/ / / /
| | | * | | | Merge branch '10.0' into 10.1Sergei Golubchik2019-01-0310-0/+0
| | | |\ \ \ \ | | | | |/ / /
| | | | * | | fix RHEL8 "ambiguous python shebang" build failuresSergei Golubchik2019-01-0210-0/+0
| | | | | | |
| | * | | | | MDEV-14576 Include full name of object in message about incorrect value for ↵Sergei Golubchik2018-12-211-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | column update engines/ suites followup for c4ab352b670