What a huge content table ? Why it is very huge ?

[toutatis]

Can u see how big it is ?

Why it is 1.43 GB :S

Pls help me.

[Zachery]

Its not, there is a bug with the repair/optimize page that reports overhead incorrectly for innodb tables. Also, please don't run repair and optimize unless:

A table is ACTUALLY crashed.

[toutatis]

How can i fix it ?

i upgraded my vbulletin 4.2.2. pl1

[Mark.B]

You can't, it's a bug within the system. Just ignore it.

[toutatis]

Ok understood. But i have an another question for you.

When i must use repair/optimize tables ? How can i know that a table has crashed.

[Mark.B]

Ok understood. But i have an another question for you.

When i must use repair/optimize tables ? How can i know that a table has crashed.

You'll know it's crashed because the site (or parts of it, depending on the table) will stop working, basically.

It's not something you need to worry about. Database tables should not be repaired or optimised unless a good reason presents itself for doing so.
If you keep doing it without good reason, you could irreparably damage your database.

[toutatis]

Thank you.