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 du
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
This might help with that task:
mysqlbinlog binary_log_file_name.01 --start-datetime="2013-02-25 16:45:00"
--stop-datetime="2013-02-25 16:50:00" | grep 'DELETE\|ALTER TABLE\|PARTITION'
-Original Message-
From: shawn green [mailto:shawn.l.gr...@oracle.com]
Sent: Tuesday, February 26
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 t
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 review the code to see if their could be deletions
anywh
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:bstill...@limitedbrands.com]
> Sent: Tue
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, I
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 mig
