mariadb/storage/innobase/fts
Thirunarayanan Balathandayuthapani a02773f7c0 MDEV-34057 Inconsistent FTS state in concurrent scenarios
Problem:
=======
- This commit is a merge of mysql commit 129ee47ef994652081a11ee9040c0488e5275b14.
InnoDB FTS can be in inconsistent state when sync operation
terminates the server before committing the operation. This
could lead to incorrect synced doc id and incorrect query results.

Solution:
========
- During sync commit operation, InnoDB should pass
the sync transaction to update the max doc id
in the config table.

fts_read_synced_doc_id() : This function is used
to read only synced doc id from the config table.
2024-06-06 19:09:13 +05:30
..
fts0ast.cc Merge 10.4 into 10.5 2020-10-30 11:15:30 +02:00
fts0blex.cc Removed some warnings from InnoDB when compiled with clang 2019-08-23 22:03:54 +02:00
fts0blex.l Merge 10.1 into 10.2 2019-05-13 17:54:04 +03:00
fts0config.cc Merge 10.3 into 10.4 2021-08-18 16:51:52 +03:00
fts0fts.cc MDEV-34057 Inconsistent FTS state in concurrent scenarios 2024-06-06 19:09:13 +05:30
fts0opt.cc MDEV-33383: Replace fts_doc_id_cmp, ib_vector_sort 2024-02-12 17:01:17 +02:00
fts0pars.cc MDEV-31890: Remove COMPILE_FLAGS 2023-10-11 15:59:56 +03:00
fts0pars.y MDEV-31890: Remove COMPILE_FLAGS 2023-10-11 15:59:56 +03:00
fts0plugin.cc Merge 10.2 into 10.3 2019-05-14 17:18:46 +03:00
fts0que.cc MDEV-33383: Corrupted red-black tree due to incorrect comparison 2024-02-12 17:01:45 +02:00
fts0sql.cc Merge 10.4 into 10.5 2021-08-18 18:22:35 +03:00
fts0tlex.cc Merge 10.1 into 10.2 2019-05-13 17:54:04 +03:00
fts0tlex.l Merge 10.1 into 10.2 2019-05-13 17:54:04 +03:00
make_parser.sh Update FSF address 2019-05-11 19:25:02 +03:00
Makefile.query