MySQL Forums
Forum List  »  Optimizer & Parser

Re: Query execution plan
Posted by: Rick James
Date: May 09, 2012 09:35PM

> PRIMARY KEY (`time`)
Risky. You could get two records with the same time. (But I don't know what kind of clock has the resolution you seem to have.)

> reason for not having one big table is speed of recalling data
Have you demonstrated that it makes any difference?

Do this:
EXPLAIN PARTITIONS select * from table_288 where time <= 5706114878826086400 order by time desc limit 1 ;
Do it for both a "range" query and an "index" query.

> This query runs very fast on the majority of tables, but very slow on a few.
Provide more details, so we can discuss what is different.

> 1 CEV0L05RT.MIN 93 range
Are you saying that you have a 93-row table partitioned?

> 4,242 ILM1H03B 111,476,494 index

When it decides to be "range" is the time (5706114878826086400, or whatever) in the table? I am wondering if this leads to the diff.
Is the query just like the SELECT, above?

Options: ReplyQuote

Written By
May 08, 2012 12:38PM
May 09, 2012 11:08AM
Re: Query execution plan
May 09, 2012 09:35PM
May 10, 2012 08:29AM
May 11, 2012 07:16PM
May 14, 2012 05:27AM
May 15, 2012 07:22PM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.