4 Commits

Author	SHA1	Message	Date
Marko Mäkelä	5ff66fb0b9	Merge 10.2 into 10.3	2020-01-31 11:37:12 +02:00
Thirunarayanan Balathandayuthapani	a134ec3736	MDEV-21550 Assertion `!table->fts->in_queue' failed in fts_optimize_remove_table ... 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.	2020-01-28 18:21:00 +05:30
Monty	5478547c96	Fixed failing tests ... - Galera tests that was not updated with connection change messages - Test where out of memory error was changed (We are now using the standard out of memory error in most places) - Removed tokudb tests that uses include files that doesn't exist in MariaDB - Removed not supported mariadb startup option from option file	2018-01-30 15:04:08 +02:00
Marko Mäkelä	9fa20716b6	Remove some more error log spam. ... Do not effectively set DEBUG_DBUG='d' by setting DEBUG_DBUG='-d,...'. Instead, restore the saved value of DEBUG_DBUG. Also, split the test innodb_fts.innodb_fts_misc_debug into innodb_fts.crash_recovery and innodb_fts.misc_debug, and enable these tests for --valgrind, the latter test for --embedded, and the former tests for the non-debug server.	2017-02-08 12:36:07 +02:00