wip: customise full text indexation
actually we index almost everything in fulltext, if we updates and delete many times,like 160K SQLCatalog_deferFullTextIndexActivity
, we may have
...
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f8028010170): REPLACE INTO
full_text
VALUES
(
1385784,
'52'
), (
2408896,
'14'
), (
1385747,
'89'
), (
1385758,
'78'
), (
1385792,
'44'
), (
1385766,
'70'
), (
1385737,
'99'
), (
1385739,
'97'
), (
1385786,
'50'
), (
1385740,
'96'
), (
1385787,
'49'
), (
1385785,
'51'
), (
1385745,
'91'
), (
1385742,
'94'
), (
2408752,
'158'
), (
2408759,
'151'
), (
2408747,
'163'
), (
2408750,
'160'
), (
2408756,
'154'
), (
1385752,
'84'
), (
1385762,
'74'
), (
1385793,
'43'
), (
1386192,
'244'
), (
1385749,
'87'
), (
2408742,
'168'
), (
1385776,
'60'
), (
2408766,
'144'
), (
2408753,
'157'
), (
2408748,
'162'
), (
2408764,
'146'
), (
1385768,
'68'
), (
2408755,
'155'
), (
1385757,
'79'
), (
1385759,
'77'
), (
2408754,
'156'
), (
2408893,
'17'
), (
1385829,
'7'
), (
1385770,
'66'
), (
2408767,
'143'
), (
2408770,
'140'
), (
1385744,
'92'
), (
1385827,
'9'
), (
1385777,
'59'
), (
2408744,
'166'
), (
1385738,
'98'
), (
1385764,
'72'
), (
1385771,
'65'
), (
1385780,
'56'
), (
1385774,
'62'
), (
1385751,
'85'
), (
1385763,
'73'
), (
2408763,
'147'
), (
2408758,
'152'
), (
1385789,
'47'
), (
2408895,
'15'
), (
1385794,
'42'
), (
1385773,
'63'
), (
1385781,
'55'
), (
1385765,
'71'
), (
2408757,
'153'
), (
1385775,
'61'
), (
1385772,
'64'
), (
1385767,
'69'
), (
1385741,
'95'
), (
2408769,
'141'
), (
1385791,
'45'
), (
1385828,
'8'
), (
2408765,
'145'
), (
1385790,
'46'
), (
2408771,
'139'
), (
2408745,
'165'
), (
2408760,
'150'
), (
1385743,
'93'
), (
1385760,
'76'
), (
1385753,
'83'
), (
2408768,
'142'
), (
2408749,
'161'
), (
1385830,
'6'
), (
1385754,
'82'
), (
1385750,
'86'
), (
1385746,
'90'
), (
1385778,
'58'
), (
1385783,
'53'
), (
1385755,
'81'
), (
1385769,
'67'
), (
2408751,
'159'
), (
1385761,
'75'
), (
1385782,
'54'
), (
2408894,
'16'
), (
1385756,
'80'
), (
2408746,
'164'
), (
1385788,
'48'
), (
2408743,
'167'
), (
1385836,
'Blue-P3 1000074'
), (
1385779,
'57'
), (
1385831,
'5'
), (
2408741,
'169'
), (
2408761,
'149'
), (
2408762,
'148'
), (
1385748,
'88'
)
Connection ID (thread ID): 54
Status: NOT_KILLED
Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains
information that should help you find out what is causing the crash.
Writing a core file...
Working directory at /srv/slapgrid/slappart8/srv/runner/instance/slappart3/srv/mariadb
Resource Limits:
....
which make mariadb unavailable
to avoid this, let's first not index needless full text