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,
, February 26, 2013 11:04 AM
To: Zachary Stern; mysql@lists.mysql.com
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
STATUS
for InnoDB.
-Original Message-
From: Stillman, Benjamin [mailto:bstill...@limitedbrands.com]
Sent: Tuesday, February 26, 2013 11:04 AM
To: Zachary Stern; mysql@lists.mysql.com
Subject: RE: data loss due to misconfiguration
Are you actually querying the table (select count
Any idea what can cause this? Can it be misconfiguration? Could it be
because I'm messing with MySQL's memory usage so much, or the thread
settings?
My config is linked at the bottom, for reference. I might be doing
something terribly dumb.
The stuff I've done under # * Fine Tuning worries me
, 2013 5:11 PM
To: mysql@lists.mysql.com
Subject: Re: data loss due to misconfiguration
Hello Zachary,
On 2/26/2013 4:42 PM, Zachary Stern wrote:
Any idea what can cause this? Can it be misconfiguration? Could it be
because I'm messing with MySQL's memory usage so much, or the thread
settings
Am 26.02.2013 22:16, schrieb Zachary Stern:
It's InnoDB but it's not just about the number of rows.
The data literally isn't there. It's like rows at the end are being
dropped. We have a frontend that queries and shows the data, but it ends up
missing results.
I've asked the devs to
Hello Zachary,
On 2/26/2013 4:42 PM, Zachary Stern wrote:
Any idea what can cause this? Can it be misconfiguration? Could it be
because I'm messing with MySQL's memory usage so much, or the thread
settings?
My config is linked at the bottom, for reference. I might be doing
something terribly
