new index would work.
-Original Message-
From: Sergey Petrunya [mailto:pser...@askmonty.org]
Sent: Monday, December 14, 2009 5:58 PM
To: Manish Ranjan
Cc: mysql@lists.mysql.com
Subject: Re: different type column and keys for EXPLAIN
Manish,
On Mon, Dec 14, 2009 at 05:33:43PM +0530, Man
Already did "Analyze table" and table is up to date. It seems like optimizer
glitch only but I am not sure. Will try adding index hints.
From: vegiv...@gmail.com [mailto:vegiv...@gmail.com] On Behalf Of Johan De
Meersman
Sent: Monday, December 14, 2009 9:14 PM
To: Manish Ranjan
that the cardinality of "clark" in your lastname
index is too high, so it uses both; the cardinality for "clarke" will be
lower, and probably low enough that using just the one index becomes faster.
No guarantees, though - that's just what it looks like from here.
On Mon
I am using mysql 5.0.77 on RHEL 5. Storage engine in MyISAM.
Please refer to the below two statements. First query is checking for
lastname 'clarke' where as second query is checking for lastname 'clark'.
Rest everything is same with these two queries. However, the explain output
shows "ref"
[mailto:vegiv...@gmail.com] On Behalf Of Johan De
Meersman
Sent: Tuesday, November 24, 2009 9:56 PM
To: Manish Ranjan (Stigasoft)
Cc: mysql@lists.mysql.com
Subject: Re: MySQL Performance with large data
The amount and type of data is less the issue than the amount and type of
queries is :-) The machine
Hi,
I am using MySQL 5.0.45 in production environment. One of my tables (using
MyISAM Engine) is expected to have around 4 billion records and each record
will have 1867 bytes of data. All fields in this table are of character data
type. I have 8 GB RAM on the server, RAID 5 with 750 GB storage
