MySQL Forums
Forum List  »  Optimizer & Parser

Advanced Search
New Topic

Re: Query optimization
Posted by: Jan Kowalski
Date: May 22, 2013 08:08AM

I,ve read here http://www.mysqlperformanceblog.com/2011/10/13/when-explain-estimates-can-go-wrong/ that mysql uses “the number of rows” estimation to pick and choose indexes.
In my case explain shows 261099 rows when query uses status_modifiedgmt index without any forcement, and 260903 rows when I force type_status_date index. So why mysql stubbornly chooses status_modifiedgmt index?

Navigate: Previous Message• Next Message
Options: Reply• Quote


Subject
Views
Written By
Posted
Query optimization
2823
Jan Kowalski
May 10, 2013 05:35AM
Re: Query optimization
1360
Rick James
May 12, 2013 08:42PM
Re: Query optimization
1317
Jan Kowalski
May 15, 2013 06:45AM
Re: Query optimization
1340
Jan Kowalski
May 15, 2013 08:35AM
Re: Query optimization
1453
Rick James
May 16, 2013 08:18AM
Re: Query optimization
1389
Jan Kowalski
May 17, 2013 03:52AM
Re: Query optimization
1319
Rick James
May 17, 2013 11:47PM
Re: Query optimization
1230
Jan Kowalski
May 21, 2013 08:51AM
Re: Query optimization
1385
Jan Kowalski
May 22, 2013 08:08AM


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.