> On Sat, Mar 7, 2009 at 12:10 PM, <buf...@biffco.net> wrote: > 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 ). >
No go. Setting concurrent_insert=2 appears to make absolutely no difference and any scenario, i.e., it didn't even work as claimed for the situation where there is free space in one or more of the merge table union set. And it also made no difference for the other situation I was probing where concurrent selects failed to work after one or more of the union set constituent tables had been packed and then unpacked (and repaired, and optimized, and flushed). Kind of surprizing to think I'm the first to exercise these features. Can't help but think I'm missing something. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
