List:General Discussion« Previous MessageNext Message »
From:David Hillman Date:July 25 2006 6:21pm
Subject:Re: Row count discrepancy when converting from MyISAM to InnoDB
View as plain text  
On Jul 25, 2006, at 11:55 AM, Frank wrote:
> Why is the record count so low after conversion to InnoDB?
> Who should I believe: InnoDB or MyISAM?
> Any ideas as to what can be done to avoid loss of this many rows?

    InnoDB doesn't keep a count on number of rows, like MyISAM does.   
InnoDB only maintains an estimate of the number of rows in each  
table.  This is why "select count(*) from table" takes a long time on  
big InnoDB tables.  Usually the InnoDB count will be off by 50% or so.

http://dev.mysql.com/doc/refman/5.0/en/innodb-restrictions.html

--
David Hillman
LiveText, Inc
1.866.LiveText x235


Thread
Row count discrepancy when converting from MyISAM to InnoDBFrank25 Jul
  • Re: Row count discrepancy when converting from MyISAM to InnoDBDavid Hillman25 Jul
  • Re: Row count discrepancy when converting from MyISAM to InnoDBFrank25 Jul
  • Re: Row count discrepancy when converting from MyISAM to InnoDBDilipkumar26 Jul
    • Re: Row count discrepancy when converting from MyISAM to InnoDBPraj26 Jul