mariadb

Tree: ed008a74cf

Author	SHA1	Message	Date
Alexey Botchkov	95228dc80b	MDEV-11570 JSON_MERGE returns incorrect result. JSON merging fixed.	9 years ago
Marko Mäkelä	195241e125	Port the test innodb.doublewrite from MySQL 5.7.	9 years ago
Marko Mäkelä	83dbb2d43a	MDEV-11487 Revert InnoDB internal temporary tables from WL#7682 Post-push fix: Remove the orphaned file sess0sess.h.	9 years ago
Igor Babaev	1152b076d4	Corrected a test from func_date_add.test	9 years ago
Igor Babaev	5c69879f3b	Fixed bug mdev-11593. When a condition containing NULLIF is pushed into a materialized view/derived table the clone of the Item_func_nullif item must be processed in a special way to guarantee that the first argument points to the same item as the third argument.	9 years ago
Nirbhay Choubey	2c734e7be3	MDEV-10993: wsrep.mdev_10186 result depends on location of ... galera library Update test case.	9 years ago
Nirbhay Choubey	b800264e49	MDEV-11152: wsrep_replicate_myisam: SELECT gets replicated ... using TO Fixed the 'wsrep_replicate_myisam' check to allow only limited set of commands. Added a debug assert to discover such cases.	9 years ago
Nirbhay Choubey	d51e7f90bf	MDEV-10957: Assertion failure when dropping a myisam table ... with wsrep_replicate_myisam enabled Internal updates to system statistical tables could wrongly trigger an additional total-order replication if wsrep_repli -cate_myisam is enabled. Fixed by adding a check to skip total-order replication for stat tables.	9 years ago
Nirbhay Choubey	9d8ec1468a	MDEV-11082: Fix mysql_client_test.c (by Elena)	9 years ago
Nirbhay Choubey	da4babb86c	Fix failing galera tests.	9 years ago
Marko Mäkelä	a01bfc9fc2	MDEV-11602 InnoDB leaks foreign key metadata on DDL operations Essentially revert MDEV-6759, which addressed a double free of memory by removing the freeing altogether, introducing the memory leaks. No double free was observed when running the test suite -DWITH_ASAN. Replace some mem_heap_free(foreign->heap) with dict_foreign_free(foreign) so that the calls can be located and instrumented more easily when needed.	9 years ago
Marko Mäkelä	44da95e5ed	Merge branch '10.0' into 10.1	9 years ago
Marko Mäkelä	8375a2c1ce	MDEV-11585 Hard-code the shared InnoDB temporary tablespace ID at -1 MySQL 5.7 supports only one shared temporary tablespace. MariaDB 10.2 does not support any other shared InnoDB tablespaces than the two predefined tablespaces: the persistent InnoDB system tablespace (default file name ibdata1) and the temporary tablespace (default file name ibtmp1). InnoDB is unnecessarily allocating a tablespace ID for the predefined temporary tablespace on every startup, and it is in several places testing whether a tablespace ID matches this dynamically generated ID. We should use a compile-time constant to reduce code size and to avoid unnecessary updates to the DICT_HDR page at every startup. Using a hard-coded tablespace ID will should make it easier to remove the TEMPORARY flag from FSP_SPACE_FLAGS in MDEV-11202.	9 years ago
Marko Mäkelä	9f863a15b0	MDEV-11602 InnoDB leaks foreign key metadata on DDL operations Essentially revert MDEV-6759, which addressed a double free of memory by removing the freeing altogether, introducing the memory leaks. No double free was observed when running the test suite -DWITH_ASAN. Replace some mem_heap_free(foreign->heap) with dict_foreign_free(foreign) so that the calls can be located and instrumented more easily when needed.	9 years ago
Daniel Black	c35b8c46b4	Travis: parallel_jobs=3	9 years ago
Marko Mäkelä	6f4f9f2843	MDEV-6076 Adjust a test result. This test and result had been modified in WL#6204, but I missed it, because the test had been renamed from innodb_fts.innodb_fts_plugin to innodb_fts.plugin.	9 years ago
Alexey Botchkov	ce55094f4f	MDEV-11572 JSON_DEPTH returns wrong results. JSON depth calculation fixed.	9 years ago
Alexey Botchkov	30c231b03a	MDEV-11569 JSON_ARRAY_INSERT produces an invalid result. String insertion fixed.	9 years ago
Alexey Botchkov	beded4350f	MDEV-JSON_CONTAINS_PATH returns incorrect results and produces wrong warning. The Item_func_json_contains_path was mistakenly set with the no '*' paths limitation.	9 years ago
Alexey Botchkov	e5377be211	MDEV-11562 Assertion `js->state == JST_VALUE' failed in check_contains(json_engine_t, json_engine_t). check_contains() fixed. When an item of an array is a complex structure, it can be half-read after the end of the recursive check_contains() call. So we just manually get to it's ending.	9 years ago
Marko Mäkelä	c64edc6b83	MDEV-6076: Preserve PAGE_ROOT_AUTO_INC when emptying pages. Thanks to Zhangyuan from Alibaba for pointing out this bug. btr_page_empty(): When a clustered index root page is emptied, preserve PAGE_ROOT_AUTO_INC. This would occur during a page split. page_create_empty(): Preserve PAGE_ROOT_AUTO_INC when a clustered index root page becomes empty. Use a faster method for writing the field. page_zip_copy_recs(): Reset PAGE_MAX_TRX_ID when copying clustered index pages. We must clear the field when the root page was a leaf page and it is being split, so that PAGE_MAX_TRX_ID will continue to be 0 in clustered index non-root pages. page_create_zip(): Add debug assertions for validating PAGE_MAX_TRX_ID and PAGE_ROOT_AUTO_INC.	9 years ago
Marko Mäkelä	cb0ce5c2e9	MDEV-6076: Optimize the test. Remove unnecessary restarts by testing multiple tables across a restart. This change almost halves the execution time. Some further restarts could be removed with additional effort.	9 years ago
Marko Mäkelä	8777458a6e	MDEV-6076 Persistent AUTO_INCREMENT for InnoDB This should be functionally equivalent to WL#6204 in MySQL 8.0.0, with the notable difference that the file format changes are limited to repurposing a previously unused data field in B-tree pages. For persistent InnoDB tables, write the last used AUTO_INCREMENT value to the root page of the clustered index, in the previously unused (0) PAGE_MAX_TRX_ID field, now aliased as PAGE_ROOT_AUTO_INC. Unlike some other previously unused InnoDB data fields, this one was actually always zero-initialized, at least since MySQL 3.23.49. The writes to PAGE_ROOT_AUTO_INC are protected by SX or X latch on the root page. The SX latch will allow concurrent read access to the root page. (The field PAGE_ROOT_AUTO_INC will only be read on the first-time call to ha_innobase::open() from the SQL layer. The PAGE_ROOT_AUTO_INC can only be updated when executing SQL, so read/write races are not possible.) During INSERT, the PAGE_ROOT_AUTO_INC is updated by the low-level function btr_cur_search_to_nth_level(), adding no extra page access. [Adaptive hash index lookup will be disabled during INSERT.] If some rare UPDATE modifies an AUTO_INCREMENT column, the PAGE_ROOT_AUTO_INC will be adjusted in a separate mini-transaction in ha_innobase::update_row(). When a page is reorganized, we have to preserve the PAGE_ROOT_AUTO_INC field. During ALTER TABLE, the initial AUTO_INCREMENT value will be copied from the table. ALGORITHM=COPY and online log apply in LOCK=NONE will update PAGE_ROOT_AUTO_INC in real time. innodb_col_no(): Determine the dict_table_t::cols[] element index corresponding to a Field of a non-virtual column. (The MySQL 5.7 implementation of virtual columns breaks the 1:1 relationship between Field::field_index and dict_table_t::cols[]. Virtual columns are omitted from dict_table_t::cols[]. Therefore, we must translate the field_index of AUTO_INCREMENT columns into an index of dict_table_t::cols[].) Upgrade from old data files: By default, the AUTO_INCREMENT sequence in old data files would appear to be reset, because PAGE_MAX_TRX_ID or PAGE_ROOT_AUTO_INC would contain the value 0 in each clustered index page. In new data files, PAGE_ROOT_AUTO_INC can only be 0 if the table is empty or does not contain any AUTO_INCREMENT column. For backward compatibility, we use the old method of SELECT MAX(auto_increment_column) for initializing the sequence. btr_read_autoinc(): Read the AUTO_INCREMENT sequence from a new-format data file. btr_read_autoinc_with_fallback(): A variant of btr_read_autoinc() that will resort to reading MAX(auto_increment_column) for data files that did not use AUTO_INCREMENT yet. It was manually tested that during the execution of innodb.autoinc_persist the compatibility logic is not activated (for new files, PAGE_ROOT_AUTO_INC is never 0 in nonempty clustered index root pages). initialize_auto_increment(): Replaces ha_innobase::innobase_initialize_autoinc(). This initializes the AUTO_INCREMENT metadata. Only called from ha_innobase::open(). ha_innobase::info_low(): Do not try to lazily initialize dict_table_t::autoinc. It must already have been initialized by ha_innobase::open() or ha_innobase::create(). Note: The adjustments to class ha_innopart were not tested, because the source code (native InnoDB partitioning) is not being compiled.	9 years ago
Daniel Bartholomew	8e198336c2	bump the VERSION	9 years ago
Sergei Golubchik	8938031bc7	InnoDB: don't stop purge threads if there's work to do in slow shutdown mode don't stop purge threads until they've purged everything there is	9 years ago
Sergei Golubchik	8d770859c9	InnoDB purge thread and other bg threads in slow shutdown mode stop all bg threads that might generate new undo records to purge before stopping purge threads.	9 years ago
Sergei Golubchik	eabb0aef12	sporadic crashes of innodb.innodb_prefix_index_restart_server in slow shutdown mode purge threads really must exit only when there is nothing to purge. Restore the trx_commit_disallowed check and don't stop purge threads until all connection thread transactions are gone.	9 years ago
Daniel Black	a8e0c6fd9b	Travis: add refs for future capability - when travis catches up	9 years ago
Daniel Black	e14bdcb81c	travis: gcc-5 and gcc-6	9 years ago
Elena Stepanova	9213ac8fd8	Follow-up for `a411d7f4f6` - change in formatting of SHOW CREATE TABLE	9 years ago
Elena Stepanova	a1833ac5cc	Follow-up for `180065ebb0` - removal of redundant parentheses	9 years ago
Igor Babaev	5cf6fd3e39	Adjusted test results after merge.	9 years ago
Vladislav Vaintroub	c13b501162	Fix broken cmake -DBUILD_CONFIG=mysql_release on Windows. mysql_release.cmake set WITH_JEMALLOC=static, which makes windows builds fail since there is no jemalloc either static or shared there	9 years ago
Igor Babaev	441fa0056d	Fixed bug mdev-11488. The patch for bug mdev-10882 tried to fix it by providing an implementation of the virtual method build_clone for the class Item_cache. It's turned out that it is not easy provide a valid implementation for Item_cache::build_clone(). At the same time if the condition that can be pushed into a materialized view contains a cached item this item can be substituted for a basic constant of the same value. In such a way we can avoid building proper clones for Item_cache objects when constructing pushdown conditions.	9 years ago
Sachin Setiya	d93bbcad36	MDEV-11479 Improved wsrep_dirty_reads Updated sysvars_wsrep.result file.	9 years ago
Varun Gupta	f41bd7e545	MDEV-11060 sql/protocol.cc:532: void Protocol::end_statement(): Assertion `0' failed In file sql/opt_range.cc,when calculate_cond_selectivity_for_table() is called with optimizer_use_condition_selectivity=4 then - thd->no_errors is set to 1 - the original value of thd->no_error is not restored to its original value - this is causing the assertion to fail in the subsequent queries Fixed by restoring the original value of thd->no_errors	9 years ago
Daniel Black	e9ada86265	Travis: add lib{stemmer,xml2,pcre3}-dev	9 years ago
Sachin Setiya	0c79de2419	MDEV-11479 Improved wsrep_dirty_reads Tasks:- Changes in wsrep_dirty_reads variable 1.) Global + Session scope (Current: session-only) 2.) Can be set using command line. 3.) Allow all commands that do not change data (besides SELECT) 4.) Allow prepared Statements that do not change data 5.) Works with wsrep_sync_wait enabled	9 years ago
Sachin Setiya	25a9a3da34	Revert "MDEV-11016 wsrep_node_is_ready() check is too strict" This reverts commit `7ed5563bbe`.	9 years ago
Sergei Golubchik	44e799590e	buildbot issues * rpm upgrade fix * update test results * valgrind warning	9 years ago
Marko Mäkelä	65b4d7457e	Merge the test innodb.innodb_misc1 into innodb.innodb.	9 years ago
Jan Lindström	72cc73cea2	MDEV-10368: get_latest_version() called too often Reduce the number of calls to encryption_get_key_get_latest_version when doing key rotation with two different methods: (1) We need to fetch key information when tablespace not yet have a encryption information, invalid keys are handled now differently (see below). There was extra call to detect if key_id is not found on key rotation. (2) If key_id is not found from encryption plugin, do not try fetching new key_version for it as it will fail anyway. We store return value from encryption_get_key_get_latest_version call and if it returns ENCRYPTION_KEY_VERSION_INVALID there is no need to call it again.	9 years ago
Alexey Botchkov	d26b9f670d	MDEV-11470 JSON_KEYS accepts arguments in invalid format. Now JSON functions return warnings if arguments are invalid.	9 years ago
Sergei Golubchik	1b7a794b73	MDEV-11540 Unexpected system threads in the process list name innodb background threads as such	9 years ago
Sergei Golubchik	85416269c3	MDEV-11518 Assertion `!table \|\| (!table->read_set \|\| bitmap_is_set(table->read_set, field_index))' failed in Field_long::val_int() QUICK_RANGE_SELECT::init_ror_merged_scan() should also set and restore TABLE::vcol_set	9 years ago
Sergei Golubchik	c697ddc315	cleanup: remove unused handler table flag	9 years ago
Sergei Golubchik	b3e3356557	bugfix: reset MODE_NO_BACKSLASH_ESCAPES during vcol parsing	9 years ago
Sergei Golubchik	a9a362d3fd	Aria: test for ER_KEY_BASED_ON_GENERATED_VIRTUAL_COLUMN Aria supports virtual columns, but does not support indexes on virtual columns. Let's issue an appropriate error in this case.	9 years ago
Sergei Golubchik	9d7c3cbe18	CONNECT: simple vcol test	10 years ago
Sergei Golubchik	5d5e83277f	weird compilation fix strangely enough, ?: variant does not link in some older gcc versions: sql/sql_table.cc:6409: undefined reference to `Alter_inplace_info::ALTER_STORED_GCOL_EXPR' sql/sql_table.cc:6409: undefined reference to `Alter_inplace_info::ALTER_VIRTUAL_GCOL_EXPR'	9 years ago

1 2 3 4 5 ...

175998 Commits (ed008a74cf4cfe8619595ec71a6073a9e94f984c) All Branches Search

175998 Commits (ed008a74cf4cfe8619595ec71a6073a9e94f984c)

All Branches