summaryrefslogtreecommitdiff
path: root/mysql-test
Commit message (Collapse)AuthorAgeFilesLines
* MDEV-21669 InnoDB: Table ... contains <n> indexes inside InnoDB, which is ↵Eugene Kosov2020-02-132-2/+30
| | | | | | | | | | | | | | | | | | | | different from the number of indexes <n> defined in the MariaDB compare_keys_but_name(): do not use KEY_PART_INFO::field for Field::is_equal(). Following the logic of that code we need to compare fields of a table. But KEY_PART_INFO::field sometimes (when key part is shorter than table field) is a different field. In that case Field::is_equal() returns incorrect result and problems occur. KEY_PART_INFO::field may become some strange field in open_frm_error open_table_from_share(). I think this is an incorrect logic, some tecnhical debt. I'm not fixing it right now, because I don't have time. But I'm making Field::field_length a const class member. Then, the only fishy code which changed that field requires now a const_cast<>. I'm bringing attention to that code with it. This change should not affect logic of the program in any way.
* MDEV-20867 - Perform careful review of "Server crashes with BACKUP STAGE and ↵Sergey Vojtovich2020-02-132-45/+6
| | | | | | | | | | | | | FLUSH TABLE table_name" Reverted original patch (c2e0a0b). For consistency with "LOCK TABLE <table_name> READ" and "FLUSH TABLES WITH READ LOCK", which are forbidden under "BACKUP STAGE", forbid "FLUSH TABLE <table_name> FOR EXPORT" and "FLUSH TABLE <table_name> WITH READ LOCK" as well. It'd allow consistent fixes for problems like MDEV-18643.
* Merge branch '10.3' into 10.4Oleksandr Byelkin2020-02-11126-2025/+2531
|\
| * Merge branch '10.2' into 10.3Oleksandr Byelkin2020-02-108-20/+52
| |\
| | * Merge branch '10.1' into 10.2Oleksandr Byelkin2020-02-102-0/+17
| | |\
| | | * MDEV-21563 FTS thread aborts during shutdownThirunarayanan Balathandayuthapani2020-02-072-0/+17
| | | | | | | | | | | | | | | | | | | | - Added the test case in innodb_fts suite - Updated copyright year in row0mysql.cc
| | | * List of unstable tests for 10.1.44 releasemariadb-10.1.44Elena Stepanova2020-01-251-146/+117
| | | |
| | * | MDEV-21667 : Galera test failure on MW-336Jan Lindström2020-02-092-24/+96
| | | | | | | | | | | | | | | | | | | | | | | | Problem seems to be the fact that we did not enforce correct applier thread numbers after every command that effects them. Test changes only.
| | * | MDEV-21601 : Cleanup Galera disabled testsJan Lindström2020-02-0920-1244/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Remove those tests that will not be supported on that release. * Make sure that correct tests are disabled and have MDEVs * Sort test names This should not be merged upwards.
| | * | added warning to ignoreOleksandr Byelkin2020-02-071-2/+2
| | | |
| | * | Windows test fixOleksandr Byelkin2020-02-071-13/+14
| | | |
| | * | MDEV-21608 Assertion `n_ext == dtuple_get_n_ext(dtuple)' failed during ↵Thirunarayanan Balathandayuthapani2020-02-072-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | updation of PK - n_ext value may be less than dtuple_get_n_ext(dtuple) when PK is being updated and new record inherits the externally stored fields from delete mark old record.
| | * | MDEV-18027: Running out of file descriptors and eventual crashOleksandr Byelkin2020-02-052-2/+2
| | | | | | | | | | | | | | | | For automatic number of opened files limit take into account number of table instances for table cache
| * | | MDEV-21667 : Galera test failure on MW-336Jan Lindström2020-02-092-24/+96
| | | | | | | | | | | | | | | | | | | | | | | | Problem seems to be the fact that we did not enforce correct applier thread numbers after every command that effects them. Test changes only.
| * | | MDEV-21601 : Cleanup Galera disabled testsJan Lindström2020-02-0920-1244/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Remove those tests that will not be supported on that release. * Make sure that correct tests are disabled and have MDEVs * Sort test names This should not be merged upwards.
| * | | MDEV-21614 Wrong query results with optimizer_switch="split_materialized=on"Igor Babaev2020-02-072-0/+132
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Do not materialize a semi-join nest if it contains a materialized derived table /view that potentially can be subject to the split optimization. Splitting of materialization of such nest would help, but currently there is no code to support this technique.
| * | | MDEV-20076: SHOW GRANTS does not quote role names properlybb-10.3-MDEV-20076Oleksandr Byelkin2020-02-05101-1938/+2083
| | | | | | | | | | | | | | | | Quotes added to output.
| * | | MDEV-21195 INSERT chooses wrong partition for RANGE partitioning by DECIMAL ↵Aleksey Midenkov2020-02-022-0/+90
| | | | | | | | | | | | | | | | | | | | | | | | column Use FLOOR rounding for DECIMAL_RESULT item_expr in partition function.
| * | | MDEV-20528 innodb.purge_secondary_mdev-16222 failed in buildbot, debug sync ↵Aleksey Midenkov2020-02-022-3/+5
| | | | | | | | | | | | | | | | point wait timed out
| * | | MDEV-17798 System variable system_versioning_asof accepts wrong valuesAleksey Midenkov2020-02-022-0/+32
| | | |
| * | | MDEV-20955 versioning.update failed in buildbot with wrong result codeAleksey Midenkov2020-02-022-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Race condition when innodb_lock_wait_timeout (default 50 seconds) exceeds for 'send update', but information_schema.innodb_lock_waits still sees this wait or it my exit by timeout. My occur on overloaded host.
| * | | Merge 10.2 into 10.3Marko Mäkelä2020-01-314-1/+24
| |\ \ \ | | |/ /
| | * | MDEV-21586 Server does not start if lc_messages setting was not english.Vladislav Vaintroub2020-01-302-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixed a bug introduced in MDEV-11345, server did not start if non-english error messages were set in startup parameters. Added lc_messages=de_DE option into an existing test case.
| | * | MDEV-21550 Assertion `!table->fts->in_queue' failed in fts_optimize_remove_tableThirunarayanan Balathandayuthapani2020-01-282-0/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: ======= The problem is that InnoDB doesn't add the table in fts slots if drop table fails. InnoDB marks the table is in fts slots while processing sync message. So the consecutive alter statement assumes that table is in queue and tries to remove it. But InnoDB can't find the table in fts_slots. Solution: ========= i) Removal of in_queue in fts_t while processing the fts sync message. ii) Add the table to fts_slots when drop table fails.
| | * | List of unstable tests for 10.2.31 releasemariadb-10.2.31Elena Stepanova2020-01-261-225/+307
| | | |
| * | | List of unstable tests for 10.3.22 releasemariadb-10.3.22Elena Stepanova2020-01-261-280/+326
| | | |
| * | | Merge branch 'MDEV-21383' into 10.3Oleksandr Byelkin2020-01-252-0/+121
| |\ \ \
* | | | | MDEV-21616: Server crash when using "SET STATEMENT max_statement_time=0 FOR ↵Oleksandr Byelkin2020-02-052-0/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | desc xxx" lead to collapse Main select should be pushed first.
* | | | | MDEV-21658 Error on online ADD PRIMARY KEY after instant DROP/reorderMarko Mäkelä2020-02-052-0/+50
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | row_log_table_get_pk_old_col(): For replacing a NULL value for a column of the being-added primary key, look up the correct default value, even if columns had been instantly reordered or dropped earlier. This ought to have been broken ever since commit 0e5a4ac2532c64a545796c787354dc41d61d0e62 (MDEV-15562).
* | | | | MDEV-21645 SIGSEGV in innobase_get_computed_valueMarko Mäkelä2020-02-042-0/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ha_innobase::commit_inplace_alter_table(): After ALTER_STORED_COLUMN_ORDER, ensure that the virtual column metadata will be reloaded also when the table is not being rebuilt.
* | | | | MDEV-20625 : MariaDB asserting when enabling wsrep_onbb-10.4-MDEV-20625Jan Lindström2020-02-042-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We need to release global system variables mutex before doing wsrep_init to avoid race with next show status and we need to save wsrep_on value as it is changed on wsrep_init. Added test case.
* | | | | MDEV-20625: MariaDB asserting when enabling wsrep=onJulius Goryavsky2020-02-043-0/+21
| | | | |
* | | | | MDEV-20001 Potential dangerous regression: INSERT INTO >=100 rows fail for ↵Sachin2020-02-032-0/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | myisam table with HASH indexes Problem:- So the issue is when we do bulk insert with rows > MI_MIN_ROWS_TO_DISABLE_INDEXES(100) , We try to disable the indexes to speedup insert. But current logic also disables the long unique indexes. Solution:- In ha_myisam::start_bulk_insert if we find long hash index (HA_KEY_ALG_LONG_HASH) we will not disable the index. This commit also refactors the mi_disable_indexes_for_rebuild function, Since this is function is called at only one place, it is inlined into start_bulk_insert mi_clear_key_active is added into myisamdef.h because now it is also used in ha_myisam.cc file. (Same is done for Aria Storage engine)
* | | | | MDEV-17798 System variable system_versioning_asof accepts wrong values (10.4)Aleksey Midenkov2020-02-022-0/+32
| | | | |
* | | | | MDEV-18791 Wrong error upon creating Aria table with long index on BLOBSachin Setiya2020-02-022-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | If we have long unique key for aria engine return too long key error, because Aria does not support key on virtual generated column.
* | | | | Fixup cd2c0e013ccb5f9b009743dfd7188585a539d9b5Marko Mäkelä2020-01-311-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | The variable 'dlh' was being used uninitialized if WSREP_PROVIDER is not set.
* | | | | Added error output wsrep_print_versionMonty2020-01-291-5/+16
| | | | | | | | | | | | | | | | | | | | This helps to determinate why galera library doesn't load
* | | | | List of unstable tests for 10.4.12 releasemariadb-10.4.12Elena Stepanova2020-01-261-231/+268
| | | | |
* | | | | Post-merge fixSergei Petrunia2020-01-261-0/+1
| | | | |
* | | | | Merge branch '10.3' into 10.4Oleksandr Byelkin2020-01-252-0/+121
|\ \ \ \ \ | | |/ / / | |/| | |
| * | | | MDEV-21383: Possible range plan is not used under certain conditionsbb-10.3-mdev21383Sergei Petrunia2020-01-242-0/+121
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | [Variant 2 of the fix: collect the attached conditions] Problem: make_join_select() has a section of code which starts with "We plan to scan all rows. Check again if we should use an index." the code in that section will [unnecessarily] re-run the range optimizer using this condition: condition_attached_to_current_table AND current_table's_ON_expr Note that the original invocation of range optimizer in make_join_statistics was done using the whole select's WHERE condition. Taking the whole select's WHERE condition and using multiple-equalities allowed the range optimizer to infer more range restrictions. The fix: - Do range optimization using a condition that is an AND of this table's condition and all of the previous tables' conditions. - Also, fix the range optimizer to prefer SEL_ARGs with type=KEY_RANGE over SEL_ARGS with type=MAYBE_KEY, regardless of the key part. Computing key_and( SEL_ARG(type=MAYBE_KEY key_part=1), SEL_ARG(type=KEY_RANGE, key_part=2) ) will now produce the SEL_ARG with type=KEY_RANGE.
* | | | | fix testsOleksandr Byelkin2020-01-242-1/+2
| | | | |
* | | | | Merge branch '10.3' into 10.4Oleksandr Byelkin2020-01-2445-127/+265
|\ \ \ \ \ | | |/ / / | |/| | |
| * | | | Merge branch '10.2' into 10.3Oleksandr Byelkin2020-01-2445-127/+265
| |\ \ \ \ | | |/ / / | |/| / / | | |/ /
| | * | MDEV-21509: Work around occasional lost DEBUG_SYNCMarko Mäkelä2020-01-242-4/+10
| | | |
| | * | don't run main.ssl_system_ca in --embeddedSergei Golubchik2020-01-231-0/+2
| | | | | | | | | | | | | | | | this test needs a *server* and tries to connect with $MYSQL to it
| | * | MENT-464 ASAN MTR quick test - some failures to be investigated.Alexey Botchkov2020-01-242-13/+13
| | | | | | | | | | | | | | | | | | | | PCRE reports small frame size working with ASAN, so the test has to be ready for the minimlas possible size.
| | * | MDEV-14183: aria_pack segfaults in compress_maria_fileVlad Lesin2020-01-232-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Post-push fix. aria_pack_mdev14183 test is unstable. The fix is the following: 1. Disable the test for embedded server. 2. Create non-"transactional" Aria table in the test, as aria_pack does not support "transactional" Aria tables.
| | * | new C/C and --ssl-verify-server-cert testsSergei Golubchik2020-01-234-0/+34
| | | | | | | | | | | | | | | | | | | | tests for --ssl-verify-server-cert with system CA and with incorrect hostname
| | * | MDEV-21249 MariaDB 10.3.10 When referring to bigint to generate timestamp ↵Sergei Golubchik2020-01-212-0/+52
| | | | | | | | | | | | | | | | | | | | | | | | data in the virtual generated column, the value of the generated column does not change when the time zone changes FROM_UNIXTIME() depends on @@time_zone, so it's VCOL_SESSION_FUNC
View Lorry Controller Status