# concurrent\_insert=2 maintenace

**URL:** <https://forums.percona.com/t/concurrent-insert-2-maintenace/1014>\
**Category:** Other MySQL® Questions\
**Created:** [November 29, 2008, 4:21pm UTC](https://forums.percona.com/t/concurrent-insert-2-maintenace/1014 "2008-11-29T16:21:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![blargman](https://avatars.discourse-cdn.com/v4/letter/b/f19dbf/32.png) [@blargman](https://forums.percona.com/u/blargman)\
**Post date:** [November 29, 2008, 4:21pm UTC](https://forums.percona.com/t/concurrent-insert-2-maintenace/1014/1 "2008-11-29T16:21:40Z")

</div>

If I’m running concurrent\_insert=2 and i end up with a bunch of deleted empty rows

what’s the best way to clear those out?

shut down the server and run a myisamchk --sort ?

from what i’ve read concurrent\_insert=2 , appends to the end of the table, ignoring deleted rows for storage. which would lead to empty deleted rows, aka a bunch of empty data in the .MYD . that’s what i got from reading the docs on it anyway.

---

<div class="post-metadata">

**Author:** ![MarkRose](https://avatars.discourse-cdn.com/v4/letter/m/85f322/32.png) [@MarkRose](https://forums.percona.com/u/MarkRose)\
**Post date:** [March 21, 2009, 7:23pm UTC](https://forums.percona.com/t/concurrent-insert-2-maintenace/1014/2 "2009-03-21T19:23:49Z")

</div>

OPTIMIZE table;

Of course, that will trigger at least a write lock while that takes place.