List:General Discussion« Previous MessageNext Message »
From:Rick James Date:February 26 2013 9:14pm
Subject:RE: data loss due to misconfiguration
View as plain text  
If it is MyISAM and there is some form of corruption, you might get the symptom you see. 
Do CHECK TABLE.

information_schema has the same "flaw" in row count as SHOW TABLE STATUS for InnoDB.

> -----Original Message-----
> From: Stillman, Benjamin [mailto:BStillman@stripped]
> Sent: Tuesday, February 26, 2013 11:04 AM
> To: Zachary Stern; mysql@stripped
> Subject: RE: data loss due to misconfiguration
> 
> Are you actually querying the table (select count(*) from table_name),
> or just the stats (show table status)? Is the table Innodb?
> 
> If  you're using Innodb and aren't doing a select count (or other
> select query) on the table, then yes you'll have varying results. This
> is because unlike MyISAM, Innodb does not keep a count of the records.
> Using show table status gives just an estimation. This would be my
> first path of investigation.
> 
> http://dev.mysql.com/doc/refman/5.5/en/show-table-status.html
> 
> "The number of rows. Some storage engines, such as MyISAM, store the
> exact count. For other storage engines, such as InnoDB, this value is
> an approximation, and may vary from the actual value by as much as 40
> to 50%. In such cases, use SELECT COUNT(*) to obtain an accurate
> count."
> 
> 
> 
> -----Original Message-----
> From: Zachary Stern [mailto:zs@stripped]
> Sent: Tuesday, February 26, 2013 12:42 PM
> To: mysql@stripped
> Subject: data loss due to misconfiguration
> 
> Is such a thing possible? There are no errors or issues, but we can
> query a table, get X number of rows, query it later, and all of the
> sudden be missing a thousand rows.
> 
> I know this isn't much to go on, but I'm not even sure what information
> to provide. Will be happy to give anything you guys might be able to
> think of.
> 
> TIA.
> 
> -Zachary
> 
> ________________________________
> 
> Notice: This communication may contain privileged and/or confidential
> information. If you are not the intended recipient, please notify the
> sender by email, and immediately delete the message and any attachments
> without copying or disclosing them. LBI may, for any reason, intercept,
> access, use, and disclose any information that is communicated by or
> through, or which is stored on, its networks, applications, services,
> and devices.
> 
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:    http://lists.mysql.com/mysql

Thread
data loss due to misconfigurationZachary Stern26 Feb
  • RE: data loss due to misconfigurationBenjamin Stillman26 Feb
    • RE: data loss due to misconfigurationRick James26 Feb
      • Re: data loss due to misconfigurationZachary Stern26 Feb
        • Re: data loss due to misconfigurationReindl Harald26 Feb
          • Re: data loss due to misconfigurationZachary Stern26 Feb
            • Re: data loss due to misconfigurationshawn green26 Feb
              • RE: data loss due to misconfigurationBenjamin Stillman26 Feb