# [EMAIL PROTECTED] / 2003-09-24 17:41:29 +0300:
> the row count in SHOW TABLE STATUS is only an estimate based on 8
> dives into the index tree.
ok.
> You had a typical symptom of a fragmented table: space usage much bigger
> than you would expect.
that doesn't answer my questions :) notice the numbers:
> > mysql> SHOW TABLE STATUS LIKE 'editor_competence_product'\G
> > *************************** 1. row ***************************
> > Name: editor_competence_product
> > Type: InnoDB
> > Row_format: Fixed
> > Rows: 225198
> > ^^^^^^
here, InnoDB thinks the table has 225198 rows.
> > mysql> ALTER TABLE editor_competence_product TYPE=InnoDB;
> > Query OK, 187654 rows affected (47.34 sec)
> > Records: 187654 Duplicates: 0 Warnings: 0
here, 187654 rows is reported.
> > mysql> SHOW TABLE STATUS LIKE 'editor_competence_product'\G
> > *************************** 1. row ***************************
> > Name: editor_competence_product
> > Type: InnoDB
> > Row_format: Fixed
> > Rows: 187265
> > ^^^^^^
yet another number. what I don't understand is why the second and
third number differ.
but this question is more important, and I'd really *love* to know
an answer:
> > Also, is there a way to *measure* the fragmentation of a table? If there
> > is, how should the info be interpreted?
--
If you cc me or remove the list(s) completely I'll most likely ignore
your message. see http://www.eyrie.org./~eagle/faqs/questions.html
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
