After a few days of playing around I finally was able to come up with a
solution:
Even though it says it will be much faster to populate the table, then
add the fulltext index, it appears the opposite is true for large tables.
I built an empty copy of the table I wanted to index, added the fu
I have a smaller database but am still unable to fulltext index one of
the tables that is only about 600mb and has rougly 3.5 million rows.
I tried both 3.23.47 and 4.0.1 and in both cases it was about the same.
I watched the temporary table that it was building and in both cases
it got up t
Hi!
On Jan 21, Steve Rapaport wrote:
> Okay, does anyone know how long this will take?
> 22 million records, fulltext index on a single field, first 40 chars.
> record length 768 chars, variable.
>
> It's been running for 2 days, processlist quotes time at around 10.
> Index file still growi
My experience (atleast with the 3.23 series) is that full text indexing is
not worth the hassle if you have an existing HUGE database... I let mysql
run for about a day or two on a 20gb database (dont remember exactly how
many rows it had) before giving up (note this was using 3.23.39). I found on
