> On Sat, Mar 7, 2009 at 12:10 PM, <buf...@biffco.net> wrote: >>>> Is there a way I can restore the concurrent select feature to a >>>> working >>>> state without having to shut down the server and rebuild the entire >>>> data >>>> base? >>> >>> Usually when concurrent insert is not permitted, it's because there >>> are holes in the table that cause inserts to go somewhere other than >>> at the end of the table. >> ...ran >> REPAIR, OPTIMIZE, and FLUSH TABLES. ... Had to dump the data base, drop >> it, and then recreate it in order to get concurrent selects working >> again." > > Another way to find out whether this is the problem (yes, I know, you > already answered this question ;-) is to set concurrent_insert=2 (see > http://dev.mysql.com/doc/refman/5.0/en/concurrent-inserts.html ).
Hey thanks for pointing out that. After reading the "=2", I recall having skimmed over that section a while ago and forgotten about it. Sounds promising. I'll try it and report back. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
