MySQL Forums
Forum List  »  Optimizer & Parser

Re: Query execution plan
Posted by: Chris Slominski
Date: May 14, 2012 05:27AM

The 5706114878826086400 is a time stamp corresponding to “2012-02-06 15:00:00.0”. I’ve used a fixed value for benchmarking this query anomaly, but in general it varies. This time stamp has been used simply because it was the time of interest used in the client request where this time anomaly was observed and reported. The “(time DIV 41561539529932800)” in the range partition definition breaks the time continuum since the UNIX epoch up into 4-month chunks; the “PARTITION p133 VALUES LESS THAN (133) ENGINE = MyISAM,” table partition holds data that occurred in the 133RD four month block since the epoch. No summarizing is performed, all data is saved for potential use by analysts.

Options: ReplyQuote


Subject
Views
Written By
Posted
3010
May 08, 2012 12:38PM
1239
May 09, 2012 11:08AM
1312
May 09, 2012 09:35PM
1446
May 10, 2012 08:29AM
1389
May 11, 2012 07:16PM
Re: Query execution plan
1464
May 14, 2012 05:27AM
1217
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.