mariadb/storage/innobase/row
Thirunarayanan Balathandayuthapani 4f26aea51b MDEV-21269 Parallel merging of fts index rebuild fails
Problem:
=======
  - During alter rebuild, document read from old table is tokenzied
parallelly by innodb_ft_sort_pll_degree threads and stores it
in respective merge files. While doing the parallel merge, InnoDB
wrongly skips the root level selection of merging buffer records.
So it leads to insertion of merge records in non-ascending order.

Solution:
==========
  Build selection tree for the root level also. So that root of
selection tree can always contain sorted buffer.
2020-05-17 11:43:25 +05:30
..
row0ext.cc Merge 10.2 into 10.3 2019-05-14 17:18:46 +03:00
row0ftsort.cc MDEV-21269 Parallel merging of fts index rebuild fails 2020-05-17 11:43:25 +05:30
row0import.cc Merge 10.2 into 10.3 2020-05-15 19:11:57 +03:00
row0ins.cc MDEV-22456 Dropping the adaptive hash index may cause DDL to lock up InnoDB 2020-05-15 17:23:08 +03:00
row0log.cc MDEV-22456 Dropping the adaptive hash index may cause DDL to lock up InnoDB 2020-05-15 17:23:08 +03:00
row0merge.cc Merge 10.2 into 10.3 2020-05-15 19:11:57 +03:00
row0mysql.cc Merge 10.2 into 10.3 2020-05-15 19:11:57 +03:00
row0purge.cc Merge 10.2 into 10.3 2020-05-15 17:55:01 +03:00
row0quiesce.cc Merge 10.2 into 10.3 2019-05-14 17:18:46 +03:00
row0row.cc Merge branch '10.2' into 10.3 2020-05-04 16:47:11 +02:00
row0sel.cc Merge 10.2 into 10.3 2020-05-15 19:11:57 +03:00
row0trunc.cc Merge 10.2 into 10.3 2020-05-15 19:11:57 +03:00
row0uins.cc Merge branch '10.2' into 10.3 2020-05-04 16:47:11 +02:00
row0umod.cc Merge branch '10.2' into 10.3 2020-05-04 16:47:11 +02:00
row0undo.cc Merge branch '10.2' into 10.3 2020-05-04 16:47:11 +02:00
row0upd.cc Merge branch '10.2' into 10.3 2020-05-04 16:47:11 +02:00
row0vers.cc Merge 10.2 into 10.3 2020-05-15 17:55:01 +03:00