summaryrefslogtreecommitdiff
path: root/mysql-test
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'bb-10.2-ext' into 10.3Marko Mäkelä2017-06-02306-4472/+9453
|\ | | | | | | | | | | This excludes MDEV-12472 (InnoDB should accept XtraDB parameters, warning that they are ignored). In other words, MariaDB 10.3 will not recognize any XtraDB-specific parameters.
| * MDEV-12930 Testing SEQUENCE objectMonty2017-05-305-2/+150
| | | | | | | | | | | | | | | | | | Fixed the following things from the above MDEV: - Ensure the user has INSERT privilege when generating new sequence values with NEXT VALUE FOR or SETVAL() - Fixed bug in InnoDB when generating several sequence values in one statement - Ensure that read_set is up to date before calling ha_sequence::ha_write_row() - This is only a potential bug with storage engines that trusts the column maps completely
| * Updated test caseMonty2017-05-301-1/+1
| |
| * SP stack tracehalfspawn2017-05-2911-13/+53
| |
| * MDEV-12803 Improve function parameter data type controlAlexander Barkov2017-05-2918-157/+788
| |
| * Adding tests for MDEV-9410 VIEW over a ROLLUP query reports too large columnsAlexander Barkov2017-05-272-0/+45
| | | | | | | | The fix for MDEV-12866 fixed this problem as well. Adding tests only.
| * Adding tests for MDEV-12861 FIRST_VALUE() does not preserve the exact data typeAlexander Barkov2017-05-272-0/+24
| | | | | | | | Recent changes in Type_handler fixed this problem. Adding tests only.
| * Adding tests for MDEV-9408 CREATE TABLE SELECT MAX(int_column) creates ↵Alexander Barkov2017-05-272-0/+60
| | | | | | | | | | | | different columns for table vs view Recent fixes in Type_handler fixed this problem. Adding tests only.
| * Adding tests for MDEV-9406 CREATE TABLE..SELECT creates different columns ↵Alexander Barkov2017-05-272-0/+57
| | | | | | | | | | | | | | for IFNULL() and equivalent COALESCE,CASE,IF Recent changes in Type_handler fixed this problem as well. Adding tests only.
| * MDEV-10309 COALESCE(12345678900) makes a column of a wrong type and ↵Alexander Barkov2017-05-272-0/+23
| | | | | | | | | | | | | | | | truncates the data Previous fixes in Type_handler (see the patch for MDEV-12875, MDEV-12886, MDEV-12916) fixed this problem as well. Adding only the test from the report.
| * Merge tag 'mariadb-10.2.6' into bb-10.2-extAlexander Barkov2017-05-26207-2443/+4975
| |\
| | * Additions to 10.2.6 unstable-tests listmariadb-10.2.6Elena Stepanova2017-05-151-8/+9
| | |
| | * MDEV-10804 main.stat_tables_par fails sporadically in buildbotMichael Widenius2017-05-113-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This was because of two issues: - thr_multi_lock_after_thr_lock needed to be hit 3 times before go2 could be signaled, because 2 of these happened before statistics_update_start was reached. - The original code didn't take into accunt that thr_locks can be executed in any random order, which caused sporadic failures when waiting for 1 lock of 3, as if the locks where in different order, there would be a dead-lock. Fixed by introducing thr_multi_lock_before_thr_lock which is deterministic. - Some of the test failures where not noticed as the DEBUG_SYNC timeout would cause the test to pass (after 300 seconds).
| | * MDEV-12776 Do not create the InnoDB temporary tablespace in innodb_read_only ↵Marko Mäkelä2017-05-101-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | mode The InnoDB temporary tablespace is only usable if innodb_read_only=OFF. It is useless to create the tablespace in read-only mode, because CREATE TEMPORARY TABLE is disallowed if innodb_read_only, and nothing can we written to the temporary tablespace if no temporary tables can be created.
| | * MDEV-12754 innodb.truncate_debug fails in buildbot with embedded due to ↵Sergei Golubchik2017-05-104-4/+4
| | | | | | | | | | | | | | | | | | semaphore wait fix sporadic innodb.truncate_purge_debug failures
| | * fix 32 bit platform testOleksandr Byelkin2017-05-101-64/+201
| | |
| | * skip innodb.innodb_xtradb_compat on WindowsSergei Golubchik2017-05-101-0/+1
| | | | | | | | | | | | | | | because it tests for variables that aren't compiled for Windows, like --innodb-priority-cleaner
| | * Fix of emulated variables comments to reflect reality.Oleksandr Byelkin2017-05-102-14/+518
| | |
| | * MDEV-12762 Some files in current 10.2 tree seem to be reverted to an old stateMarko Mäkelä2017-05-1065-684/+101
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The issue was a bad merge of MDEV-12253 from 10.1 to 10.2 in commit f9cc391863ab962e8c8a8a8a676d730498eb8d6f. In that merge, I wrongly assumed that all test file conflicts for mysql-test/suite/encryption had been properly resolved in bb-10.2-MDEV-12253 (commit 76aa6be77635c7017459ce33b41c837c9acb606d) while in fact, some files there had been copied from the 10.1 branch. This commit is based on a manually done conflict resolution of the mysql-test/suite/encryption on the same merge, applied to the current 10.2 branch. As part of this commit, the test encryption.innodb-bad-key-change4 which was shortly disabled due to MDEV-11336 will be re-enabled again. (While the test enables innodb_defragment, it does not fail even though enabling innodb_defragment currently has no effect.)
| | * List of unstable tests for 10.2.6 (initial 10.2 version for GA)Elena Stepanova2017-05-101-375/+273
| | |
| | * MDEV-12750 Fix crash recovery of key rotationMarko Mäkelä2017-05-092-26/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When MySQL 5.7.9 was merged to MariaDB 10.2.2, an important debug assertion was omitted from mlog_write_initial_log_record_low(). mlog_write_initial_log_record_low(): Put back the assertion mtr_t::is_named_space(). fil_crypt_start_encrypting_space(), fil_crypt_rotate_page(): Call mtr_t::set_named_space() before modifying any pages. fsp_flags_try_adjust(): Call mtr_t::set_named_space(). This additional breakage was introduced in the merge of MDEV-11623 from 10.1. It was not caught because of the missing debug assertion in mlog_write_initial_log_record_low(). Remove some suppressions from the encryption.innodb-redo-badkey test.
| | * MDEV-12472: InnoDB should accept XtraDB parameters, warning that they are ↵Jan Lindström2017-05-093-0/+510
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ignored Added a new file ha_xtradb.h where XtraDB parameters are defined. This file is included in two places to avoid too intrusive change to ha_innodb.cc that would make future merges harder. innodb_show_locks_held and innodb_show_verbose_locks should be implemented (but on different commit).
| | * Added tests for MDEV-11724, MDEV-11725, MDEV-11726.Jan Lindström2017-05-092-0/+118
| | |
| | * MDEV-10332 support for OpenSSL 1.1 and LibreSSLSergei Golubchik2017-05-093-8/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | post-review fixes: * move all ssl implementation related ifdefs/defines to one file (ssl_compat.h) * work around OpenSSL-1.1 desire to malloc every EVP context by run-time checking that context allocated on the stack is big enough (openssl.c) * use newer version of the AWS SDK for OpenSSL 1.1 * use get_dh2048() function as generated by openssl 1.1 (viosslfactories.c)
| | * MDEV-10332 support for OpenSSL 1.1 and LibreSSLGeorg Richter2017-05-099-19/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Initial support tested against OpenSSL 1.0.1, 1.0.2, 1.1.0, Yassl and LibreSSL not working on Windows with native SChannel support, due to wrong cipher mapping: Latter one requires push of CONC-241 fixes. Please note that OpenSSL 0.9.8 and OpenSSL 1.1.0 will not work: Even if the build succeeds, test cases will fail with various errors, especially when using different tls libraries or versions for client and server.
| | * Fix test failure on Windows.Jan Lindström2017-05-091-0/+1
| | | | | | | | | | | | In windows error message contains .exe.
| | * Merge branch '10.1' into 10.2Sergei Golubchik2017-05-0942-138/+879
| | |\ | | | | | | | | | | | | | | | | Revert commit db0917f68f, because the fix for MDEV-12696 is coming from 5.5 and 10.1 in this merge.
| | | * MDEV-12696 Crash with LOAD XML and non-updatable VIEW columnSergei Golubchik2017-05-093-0/+33
| | | | | | | | | | | | | | | | extend the fix from 5.5 (in read_sep_field()) to apply to read_xml_field()
| | | * Merge branch '10.0' into 10.1Sergei Golubchik2017-05-084-0/+85
| | | |\
| | | | * Merge branch '5.5' into 10.0Sergei Golubchik2017-05-082-0/+81
| | | | |\
| | | | | * Fixed the bug mdev-12673.Igor Babaev2017-05-042-0/+81
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch corrects the fix for the bug mdev-10693. It is critical for the function get_best_combination() not to call create_ref_for_key() for constant tables. This bug could manifest itself only in multi-table subqueries where one of the tables is accessed by a constant primary key.
| | | | * | MDEV-12635 innodb.log_file_size fails when run with ValgrindMarko Mäkelä2017-05-052-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In MariaDB Server before 10.2, InnoDB will not be shut down properly if startup fails. So, Valgrind failures are to be expected. Disable the test under Valgrind. In 10.2, it should pass with Valgrind.
| | | * | | MDEV-12628: innodb.innodb_bug14147491 sporadically fails in buildbot due to ↵Jan Lindström2017-05-082-18/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | wrong error number Actual error number returned from the query depends what point corrupted page is accessed, is it accessed when we read one of the pages for result set or is it accessed during background page read.
| | | * | | MDEV-12627: innodb.innodb_bug14147491 does not do proper cleanupJan Lindström2017-05-082-6/+0
| | | | | | | | | | | | | | | | | | | | | | | | Removed creation of unused backup file and unused variables.
| | | * | | Merge pull request #362 from ↵Jan Lindström2017-05-024-4/+8
| | | |\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | grooverdan/10.1-MDEV-XXXX-mysqltest-replace-regex-vars MDEV-12522: mysqltest replace regex + sys_vars.sysvars_wsrep test to be version independent
| | | | * | | tests: sys_vars.sysvars_wsrepDaniel Black2017-04-182-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Rather than bumping the version again, * d036cc9b2f595cac1453f2a251515c6b9a408521, and again * 5a4ec8e60b10c176af1dd84157e1d15cf905637b, and again * 7f19330c595e3183d079fe2c18eecc74740e8f83; Just accept version numbers change. Also accept that people may want to test this against more than one version.
| | | | * | | Add replace_regex to not ignore the regex in "$var /regex/val/"Daniel Black2017-04-182-2/+6
| | | | | | |
| | | * | | | Updated list of unstable tests for 10.1.23Elena Stepanova2017-04-291-79/+136
| | | | | | |
| | | * | | | Merge branch '10.0' 10.1Sergei Golubchik2017-04-2838-50/+920
| | | |\ \ \ \ | | | | | |/ / | | | | |/| |
| | | | * | | Merge branch '5.5' into bb-10.0-merge-5.5bb-10.0-merge-5.5Oleksandr Byelkin2017-04-252-0/+35
| | | | |\ \ \ | | | | | | |/ | | | | | |/|
| | | | | * | Fixed the bug mdev-10693.Igor Babaev2017-04-242-0/+36
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The code that chooses between materialization of a non-correlated IN subquery and its transformation into an EXISTS correlated subquery assumes that the execution plan for the outer select has been already built. However it was not always so if subqueries occurred in the expressions used for ref access to tables of the outer select. A call of the function create_ref_for_key() in get_best_combination() could trigger a premature execution of the above mentioned code when the execution plan structures for the outer select were not fully built. This could cause a crash of the server. The fix postpones the calls of create_ref_for_key() until the structures for the execution plan is fully built.
| | | | * | | Add and adjust a test from MySQL:Marko Mäkelä2017-04-242-0/+175
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | commit 1198267c331b045b9cad26be72b1a5b4f8930a79 Author: Thirunarayanan Balathandayuthapani <thirunarayanan.balathandayuth@oracle.com> Date: Fri Aug 26 11:00:44 2016 +0530 Bug #20989615 INNODB AUTO_INCREMENT PRODUCES SAME VALUE TWICE The code fix is already present.
| | | | * | | Add and adjust a test from MySQL:Marko Mäkelä2017-04-243-0/+98
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | commit 12343617922cfd9c48ee84ad6ecf53068d822010 Author: Thirunarayanan Balathandayuthapani <thirunarayanan.balathandayuth@oracle.com> Date: Fri Jul 15 14:39:37 2016 +0530 Bug #23475211 COMBINING ALTER OPERATIONS TRIGGERS TABLE REBUILD The code fix is already present.
| | | | * | | MDEV-12495 Conditional jump depends on uninitialised value for: SELECT NULL ↵Alexander Barkov2017-04-222-0/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | UNION geom_expression
| | | | * | | Fixed bug mdev-10053.Igor Babaev2017-04-215-12/+94
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The implementation of the walk method for the class Item_in_subselect was missing. As a result the method never traversed the left operand of any IN subquery predicate. Item_exists_subselect::exists2in_processor() that performs the Exist-To-In transformation calls the walk method to collect info on outer references. As the walk method did not traverse the left operands of the IN subqueries the outer references there were not taken into account and some subqueries that were actually correlated were marked as uncorrelated. It could lead to an attempt of the materialization of such a subquery. Also added a cleanup for some test cases merged from 5.5.
| | | | * | | Merge branch '5.5' into 10.0Sergei Golubchik2017-04-2127-48/+502
| | | | |\ \ \ | | | | | |/ /
| | | | | * | Fix use of `require` in mysql-test-run.Oleksandr Byelkin2017-04-193-10/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The motivation for this is that Perl is moving towards not having current directory ./ in @INC by default. This is causing mysql-test-run.pl to fail in latest Debian Unstable: https://lists.debian.org/debian-devel-announce/2016/08/msg00013.html However, we have `use "lib"`, there is no need for current directory in @INC, except for a gross hack. In mtr_cases.pm, there is a `require "mtr_misc.pl"`, which hides mtr_misc.pl away in mtr_cases namespace. And things only work because mysql-test-run.pl loads it with a different name, `require "lib/mtr_misc.pl"`! (Perl will `require` only once for each unique filename). Fix this by only using `require` in main program, and referencing functions with :: scope from other namespaces. For multi-use in different namespaces, proper `use` modules should be used. Signed-off-by: Kristian Nielsen <knielsen@knielsen-hq.org>
| | | | | * | Merge remote-tracking branch 'mysql/5.5' into 5.5mariadb-5.5.55Sergei Golubchik2017-04-1113-26/+177
| | | | | |\ \
| | | | | | * | Bug #25717383: MYSQLDUMP MAY EXECUTE ANY ARBITRARY QUERYmysql-5.5.55Bharathy Satish2017-03-182-0/+113
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | While writing comments if database object names has a new line character, then next line is considered a command, rather than a comment. This patch fixes the way comments are constructed in mysqldump. (cherry picked from commit 1099f9d17b1c697c2760f86556f5bae7d202b444)
| | | | | | * | BUG#25575605: SETTING --SSL-MODE=REQUIRED SENDS CREDENTIALS BEFORE VERIFYING ↵Ramil Kalimullin2017-03-102-14/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | SSL CONNECTION MYSQL_OPT_SSL_MODE option introduced. It is set in case of --ssl-mode=REQUIRED and permits only SSL connection. (cherry picked from commit 3b2d28578c526f347f5cfe763681eff365731f99)
View Lorry Controller Status