On Sat, Mar 7, 2009 at 12:10 PM, <buford@stripped> 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
>> 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.
> Thanks for the suggestion, but apparently you missed the preceding
> sentence in my post, which said, "...I unpacked the table, even 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
No, I saw it. I was just commenting that this is the usual reason why
it doesn't work. I should have been clearer about that.
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