Comments on: Introducing MySQL Table Maintainer

By: Karthik

Karthik — Wed, 21 Jan 2009 17:11:14 +0000

Well, it gives a more detailed report for starters.
Also, it would be great if it gave a summary at the end of the run as to how many tables were checked/which had issues so that further investigation is possible. This helps for people like me who have 40k + tables. mysqlchk scrolls too fast and its a pain to keep looking at the OKs to see if anything is not OK!

By: Xaprb

Xaprb — Sat, 31 Mar 2007 00:27:39 +0000

No extra locks like LOCK TABLES. But I'm seriously considering deleting this tool, since as Peter pointed out it (mostly) duplicates the functionality of mysqlcheck :(

By: Sheeri

Sheeri — Fri, 30 Mar 2007 13:33:02 +0000

Do you mean it doesn't lock at all? Or just doesn't lock on top of the commands like REPAIR?

By: Xaprb

Xaprb — Mon, 26 Mar 2007 16:41:57 +0000

Wait, how did I miss mysqlcheck? I spent several evenings duplicating a tool that's already provided :-(

I will have to research more carefully next time!

By: Peter Zaitsev

Peter Zaitsev — Mon, 26 Mar 2007 15:57:03 +0000

Hm, Why are you looking at myisamchk at all ? Especially if you're working with multiple storage engines you're much better of using mysqlcheck instead. myisamchk has some features which are myisam specific and not available via mysqlcheck.