Aleksey Midenkov e056efdd6c MDEV-25004 Missing row in FTS_DOC_ID_INDEX during DELETE HISTORY ... 1. In case of system-versioned table add row_end into FTS_DOC_ID index in fts_create_common_tables() and innobase_create_key_defs(). fts_n_uniq() returns 1 or 2 depending on whether the table is system-versioned. After this patch recreate of FTS_DOC_ID index is required for existing system-versioned tables. If you see this message in error log or server warnings: "InnoDB: Table db/t1 contains 2 indexes inside InnoDB, which is different from the number of indexes 1 defined in the MariaDB" use this command to fix the table: ALTER TABLE db.t1 FORCE; 2. Fix duplicate history for secondary unique index like it was done in MDEV-23644 for clustered index (932ec586aa). In case of existing history row which conflicts with currently inseted row we check in row_ins_scan_sec_index_for_duplicate() whether that row was inserted as part of current transaction. In that case we indicate with DB_FOREIGN_DUPLICATE_KEY that new history row is not needed and should be silently skipped. 3. Some parts of MDEV-21138 (7410ff436e) reverted. Skipping of FTS_DOC_ID index for history rows made problems with purge system. Now this is fixed differently by p.2. 4. wait_all_purged.inc checks that we didn't affect non-history rows so they are deleted and purged correctly. Additional FTS fixes fts_init_get_doc_id(): exclude history rows from max_doc_id calculation. fts_init_get_doc_id() callback is used only for crash recovery. fts_add_doc_by_id(): set max value for row_end field. fts_read_stopword(): stopwords table can be system-versioned too. We now read stopwords only for current data. row_insert_for_mysql(): exclude history rows from doc_id validation. row_merge_read_clustered_index(): exclude history_rows from doc_id processing. fts_load_user_stopword(): for versioned table retrieve row_end field and skip history rows. For non-versioned table we retrieve 'value' field twice (just for uniformity). FTS tests for System Versioning now include maybe_versioning.inc which adds 3 combinations: 'vers' for debug build sets sysvers_force and sysvers_hide. sysvers_force makes every created table system-versioned, sysvers_hide hides WITH SYSTEM VERSIONING for SHOW CREATE. Note: basic.test, stopword.test and versioning.test do not require debug for 'vers' combination. This is controlled by $modify_create_table in maybe_versioning.inc and these tests run WITH SYSTEM VERSIONING explicitly which allows to test 'vers' combination on non-debug builds. 'vers_trx' like 'vers' sets sysvers_force_trx and sysvers_hide. That tests FTS with trx_id-based System Versioning. 'orig' works like before: no System Versioning is added, no debug is required. Upgrade/downgrade test for System Versioning is done by innodb_fts.versioning. It has 2 combinations: 'prepare' makes binaries in std_data (requires old server and OLD_BINDIR). It tests upgrade/downgrade against old server as well. 'upgrade' tests upgrade against binaries in std_data. Cleanups: Removed innodb-fts-stopword.test as it duplicates stopword.test		2022-12-27 00:02:02 +03:00
..
dict0boot.cc	Merge 10.2 into 10.3	2020-09-09 13:06:46 +03:00
dict0crea.cc	MDEV-29291 Assertion `!table->fts' failed in dict_table_can_be_evicted on SHUTDOWN	2022-08-24 10:58:08 +05:30
dict0defrag_bg.cc	MDEV-29883 Deadlock between InnoDB statistics update and BLOB insert	2022-11-09 09:23:18 +02:00
dict0dict.cc	MDEV-27927 row_sel_try_search_shortcut_for_mysql() does not latch a page, violating read view isolation	2022-10-05 17:35:21 +03:00
dict0load.cc	MDEV-28980 InnoDB: Failing assertion: len <= MAX_TABLE_NAME_LEN	2022-07-25 10:28:45 +03:00
dict0mem.cc	MDEV-25004 Missing row in FTS_DOC_ID_INDEX during DELETE HISTORY	2022-12-27 00:02:02 +03:00
dict0stats.cc	MDEV-29883 Deadlock between InnoDB statistics update and BLOB insert	2022-11-09 09:23:18 +02:00
dict0stats_bg.cc	MDEV-25975 innodb_disallow_writes causes shutdown to hang	2022-04-06 08:06:49 +03:00