Hi. I have a query that has been running for 10.7 hours. It is converting a 3.6GB
MyISAM to Innodb.
38448 | copy to tmp table | alter table `MESSAGES` type=innodb
The innodb data file has increased 8.6GB in size since the command started.
How do I tell how far through the conversion the proce
Hi. I have a table with a fulltext search index on a field.
I am inserting text using UTF-8 characters (with the JDBC driver). That
includes words in English, French, Russian and Greek.
The FULLTEXT search only seems to find words in the latin charset.
Does anyone have any guidance on how I ca
cond timeframe). Having searches that don't
return all matching rows would be acceptable (but not desirable). e.g. I'm
thinking of just deleting less important rows from my large table.
Thanks in advance for any help,
Peter Bryant
___
xt index,
this is not an innodby table.
Since some of the threads were doing replace SQL I had a look at the "insert
delayed" command. However, it seems from the manual that this won't
necessarily help much with MyISAM tables.
Any help appreciated,
Regards, Peter Bryant
_
I've changed myisam_sort_buffer to 128M in the hopes that that may have sped
things up, but to no avail.
Does anyone have a) an explanation for why the index creation seems to go
slower and slower the more rows there are or b) any ideas on how to sped up
the index creation.
Regards, Peter Br
