summaryrefslogtreecommitdiff
path: root/mysql-test
Commit message (Collapse)AuthorAgeFilesLines
* List of unstable tests for 10.0.38 releasemariadb-10.0.38Elena Stepanova2019-01-291-74/+45
|
* MDEV-18016: Assertion failure on ALTER TABLE after foreign_key_checks=0Marko Mäkelä2019-01-292-0/+20
| | | | | | | | | ha_innobase::commit_inplace_alter_table(): Do not crash if innobase_update_foreign_cache() returns an error. It can return an error on ALTER TABLE if an inconsistent FOREIGN KEY constraint was created earlier when SET foreign_key_checks=0 was in effect. Instead, report a warning to the client that constraints cannot be loaded.
* MDEV-18256 Duplicated call to dict_foreign_remove_from_cache()Marko Mäkelä2019-01-292-0/+19
| | | | | ha_innobase::prepare_inplace_alter_table(): Filter out duplicates from ha_alter_info->alter_info->drop_list.elements.
* MDEV-18222: Duplicated call to dict_foreign_remove_from_cache()Marko Mäkelä2019-01-292-0/+25
| | | | | innobase_rename_column_try(): Declare fk_evict as std::set instead of std::list, in order to filter out duplicates.
* Merge branch '5.5' into 10.0Oleksandr Byelkin2019-01-283-0/+49
|\
| * disable an old testSergei Golubchik2019-01-281-0/+1
| | | | | | | | | | @@open_files_limit now behaves differenly and cannot be used to skip the test anymore.
| * Crude "auto-load-data-local-infile" modemariadb-5.5.63Sergei Golubchik2019-01-272-0/+48
| | | | | | | | | | | | | | Disable LOAD DATA LOCAL INFILE suport by default and auto-enable it for the duration of one query, if the query string starts with the word "load". In all other cases the application should enable LOAD DATA LOCAL INFILE support explicitly.
* | Merge branch 'merge-perfschema-5.6' into 10.0Oleksandr Byelkin2019-01-282-2/+7
|\ \
| * | 5.6.43Oleksandr Byelkin2019-01-242-2/+7
| | |
| * | 5.6.42Sergei Golubchik2018-10-271-7/+7
| | |
* | | Merge branch '5.5' into 10.0Oleksandr Byelkin2019-01-285-0/+91
|\ \ \ | | |/ | |/|
| * | Bug #28499924: INCORRECT BEHAVIOR WITH UNION IN SUBQUERYSergei Golubchik2019-01-232-0/+42
| | | | | | | | | | | | test case
| * | MDEV-17085: CHECKSUM TABLE EXTENDED does not work correctlyOleksandr Byelkin2019-01-163-0/+49
| | | | | | | | | | | | The problem was in calculating of the mask to clear unused null bits in case of using full byte.
* | | MDEV-18255: Server crashes in Bitmap<64u>::intersectVarun Gupta2019-01-242-0/+29
| | | | | | | | | | | | | | | | | | | | | Calling st_select_lex::update_used_tables in JOIN::optimize_unflattened_subqueries only when we are sure that the join have not been cleaned up. This can happen for a case when we have a non-merged semi-join and an impossible where which would lead to the cleanup of the join which has the non-merged semi-join
* | | MDEV-17376 Server fails to set ADD_PK_INDEX, DROP_PK_INDEX if unique index ↵Thirunarayanan Balathandayuthapani2019-01-244-15/+179
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | nominated as PK Problem: ======== Server fails to notify the engine by not setting the ADD_PK_INDEX and DROP_PK_INDEX When there is a i) Change in candidate for primary key. ii) New candidate for primary key. Fix: ==== Server sets the ADD_PK_INDEX and DROP_PK_INDEX while doing alter for the above problematic case.
* | | MDEV-17803 Row-based event is not applied when table map id is greaterAndrei Elkin2019-01-235-0/+154
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 32 bit int Row-based slave applier could not parse correctly the table id when the value exceeded the max of 32 bit unsigned int. The reason turns out in that the being parsed value placeholder was sized as 4 bytes. The type is fixed to ulonglong. Additionally the patch works around Rows_log_event::m_table_id 4 bytes size on 32 bits platforms. In case of last_table_id value overflows the 4 byte max, there won't be the zero value for m_table_id generated and the first wrapped-around value is one, this is thanks to excluding UINT_MAX32 + 1 from TABLE_SHARE::table_map_id.
* | | Bug#28867993: POSSIBLE ISSUE WITH MYSQL SERVER RESTARTSergei Golubchik2019-01-232-0/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | on startup innodb is checking whether files "ib_logfileN" (for N from 1 to 100) exist, and whether they're readable. A non-existent file aborted the scan. A directory instead of a file made InnoDB to fail. Now it treats "directory exists" as "file doesn't exist".
* | | MDEV-15925 FRM_MAX_SIZE too low for some use casesSergei Golubchik2019-01-212-2/+11
| | | | | | | | | | | | increase to 1M
* | | MDEV-14440: Assertion `inited==RND' failed in handler::ha_rnd_endVarun Gupta2019-01-182-0/+49
| | | | | | | | | | | | | | | | | | | | | | | | | | | In the function QUICK_RANGE_SELECT::init_ror_merged_scan we create a seperate handler if the handler in head->file cannot be reused. The flag free_file tells us if we have a seperate handler or not. There are cases where you might create a handler and then there might be a failure(running ALTER) and then we have to revert the handler back to the original one. The code does that but it does not reset the flag 'free_file' in this case. Also backported f2c418079def.
* | | MDEV-17475: Increase maximum possible value for table_definition_cache to ↵Oleksandr Byelkin2019-01-162-11/+11
| | | | | | | | | | | | | | | | | | match table_open_cache Allow table definition cache be bigger than open table cache (due to problem with VIEWs and prepared statements).
* | | Merge pull request #973 from tempesta-tech/tt-10.0-MDEV-16499-virtual-innodbMarko Mäkelä2019-01-142-0/+26
|\ \ \ | | | | | | | | MDEV-16499 ER_NO_SUCH_TABLE_IN_ENGINE followed by "Please drop the table and recreate" upon adding FULLTEXT key to table with virtual column
| * | | MDEV-16499 [10.1] ER_NO_SUCH_TABLE_IN_ENGINE followed by "Please drop the ↵Eugene Kosov2018-11-302-0/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | table and recreate" upon adding FULLTEXT key to table with virtual column There was an incorrect check for MariaDB and InnoDB tables fields count. Corruption was reported when there was no corruption. Also, a warning message had incorrect field numbers for both MariaDB and InnoDB tables. ha_innobase::open(): fixed check and message
* | | | MDEV-13784: query causes seg faultVarun Gupta2019-01-064-4/+77
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When we have a nested subquery then a subquery that was a dependent subquery may change to an independent one when we optimizer the inner subqueries. This is handled st_select_lex::optimize_unflattened_subqueries. Currently a subquery that was changed to independent from dependent after optimization phase incorrectly shows dependent in the output of Explain, this happens because we don't update used_tables for the WHERE clause, ON clause, etc after the optimization phase.
* | | | Merge branch '5.5' into 10.0Sergei Golubchik2019-01-032-4/+4
|\ \ \ \ | | |/ / | |/| |
| * | | fix the test for 2019Sergei Golubchik2019-01-022-4/+4
| | | |
* | | | MDEV-18041 Database corruption after renaming a prefix-indexed columnEugene Kosov2018-12-292-0/+34
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is a regression after MDEV-13671. The bug is related to key part prefix lengths wich are stored in SYS_FIELDS. Storage format is not obvious and was handled incorrectly which led to data dictionary corruption. SYS_FIELDS.POS actually contains prefix length too in case if any key part has prefix length. innobase_rename_column_try(): fixed prefixes handling Tests for prefixed indexes added too. Closes #1063
* | | | Merge branch '5.5' into 10.0Sergei Golubchik2018-12-202-5/+31
|\ \ \ \ | |/ / /
| * | | MDEV-16987 - ALTER DATABASE possible in read-only modeSergey Vojtovich2018-12-132-0/+24
| | | | | | | | | | | | | | | | Forbid ALTER DATABASE under read_only.
* | | | MDEV-17720 slave_ddl_exec_mode=IDEMPOTENT does not handle DROP DATABASESachin2018-12-192-0/+33
| | | | | | | | | | | | | | | | Relevant if exists flag are added for create database and drop database.
* | | | MDEV-17589: Stack-buffer-overflow with indexed varchar (utf8) fieldbb-10.0-varunVarun Gupta2018-12-192-0/+56
| | | | | | | | | | | | | | | | | | | | | | | | Create a new constant MAX_DATA_LENGTH_FOR_KEY. Replace the value of MAX_KEY_LENGTH to also include the LENGTH and NULL BYTES of a field.
* | | | Backported MDEV-11196(e4d10e09cf31) and MDEV-10360(8a8ba1949bf4) to 10.0Varun Gupta2018-12-192-0/+201
| | | |
* | | | MDEV-6453: Assertion `inited==NONE || (inited==RND && scan)' failed in ↵Varun Gupta2018-12-162-0/+35
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | handler::ha_rnd_init(bool) with InnoDB, joins, AND/OR conditions The inited parameter handler is not initialised when we do a quick_select after a table scan.
* | | | MDEV-17833 ALTER TABLE is not enforcing prefix index size limitEugene Kosov2018-12-112-0/+63
| | | | | | | | | | | | | | | | | | | | ha_innobase::prepare_inplace_alter_table(): check max column length for every index in a table, not just added in this particular ALTER TABLE with ADD INDEX ones.
* | | | MDEV-17032: Estimates are higher for partitions of a table with ↵Varun Gupta2018-12-072-0/+161
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | @@use_stat_tables= PREFERABLY The problem here is EITS statistics does not calculate statistics for the partitions of the table. So a temporary solution would be to not read EITS statistics for partitioned tables. Also disabling reading of EITS for columns that participate in the partition list of a table.
* | | | MDEV-17898 FLUSH PRIVILEGES crashes server with segfaultSergei Golubchik2018-12-062-0/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | merge_role_db_privileges() was remembering pointers into Dynamic_array acl_dbs, and later was using them, while pushing more elements into the array. But pushing can cause realloc, and it can invalidate all pointers. Fix: remember and use indexes of elements, not pointers.
* | | | Added a testcase for mdev-17734Varun Gupta2018-12-053-0/+55
| |/ / |/| |
* | | Merge branch '5.5' into 10.0Oleksandr Byelkin2018-11-154-0/+137
|\ \ \ | |/ /
| * | MDEV-17724 Wrong result for BETWEEN 0 AND 18446744073709551615Alexander Barkov2018-11-154-0/+137
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The fix for "MDEV-17698 MEMORY engine performance regression" previously fixed this problem. - Adding the test for MDEV-17724 - Re-recording wrong results for tests: * engines/iuds/r/insert_number * engines/iuds/r/update_delete_number which started to fail since MDEV-17698
* | | fix of test suiteOleksandr Byelkin2018-11-142-2/+2
| | |
* | | MDEV-11167: InnoDB: Warning: using a partial-field key prefix in search, ↵Oleksandr Byelkin2018-11-072-0/+56
| | | | | | | | | | | | | | | | | | results in assertion failure or "Can't find record" error Fix ha_rnd_init() argument (we do not doing scan but use rnd_pos)
* | | Merge 5.5 into 10.0Marko Mäkelä2018-11-074-2/+29
|\ \ \ | |/ /
| * | fix the test to clean after itselfSergei Golubchik2018-11-011-0/+2
| | | | | | | | | | | | followup for c32f7ed235f
| * | MDEV-17377 invalid gap in auto-increment values after LOAD DATASergei Golubchik2018-11-012-0/+25
| | | | | | | | | | | | | | | reset lex->many_values for LOAD DATA, as it's used for auto-inc range size estimation.
| * | test framework manual is movedTakashi Sasaki2018-11-012-2/+2
| | |
* | | MDEV-13671 InnoDB should use case-insensitive column name comparisons like ↵Eugene Kosov2018-11-052-10/+229
| | | | | | | | | | | | | | | | | | | | | | | | | | | the rest of the server Problem affects INPLACE ALTER rename columns. innobase_rename_column_try(): some strcmp() was replaced with my_strcasecmp(), queries to update data dictionary was updated to not match column name case.
* | | MDEV-16695: Estimate for rows of derived tables is very high when we are ↵Varun Gupta2018-11-012-0/+85
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | using index_merge union For index merge union[or sort union], the estimates are not taken into account while calculating the selectivity of a condition. So instead of showing the estimates of the index merge union[or sort union], it shows estimates equal to all the records of the table. The fix for the issue is to include the selectivity of index merge union[or sort union] while calculating the selectivity of a condition.
* | | MDEV-17298 ASAN unknown-crash / READ of size 1 in my_strntoul_8bit upon ↵Alexander Barkov2018-10-312-0/+21
| | | | | | | | | | | | INSERT .. SELECT
* | | Merge branch '5.5' into 10.0Sergei Golubchik2018-10-313-5/+99
|\ \ \ | |/ /
| * | ./mtr --gdb='b mysql_parse;r'Sergei Golubchik2018-10-301-3/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | --gdb now accepts an argument, it will be passed to gdb as a command. multiple commands can be separated by a (non-standard and not escapable) delimiter - semicolon (;). Old usage with a bare --gdb continues to work too, of course. Cherry-picked c47c0ca50c4 5441bbd3b1f 339b9055791
| * | MDEV-17256 Decimal field multiplication bug.bb-5.5-hfAlexey Botchkov2018-10-302-0/+86
| | | | | | | | | | | | | | | | | | We should clear trailing zeroes in frac part. Otherwise that tail is growing quickly and forces unnecessary truncating of arguments.
View Lorry Controller Status