Re: Wrong estimation of Rows in explain
Posted by:
Rick James
Date: August 02, 2016 06:23PM
Try innodb_buffer_pool_size = 2G -- if that leads to swapping, then it is too big.
EXPLAIN's row estimate is only approximate. There is no way to make it exact. It will even estimate the number of rows in the table.
For this:
a.col1 = b.col1 and a.col2 = b.col2
have both of these:
On a: INDEX(col1, col2)
On b: INDEX(col1, col2)
That is, a composite index is better (in this case) than an index on a single column.
Subject
Views
Written By
Posted
2008
July 27, 2016 06:19AM
1010
July 27, 2016 08:55AM
1063
July 27, 2016 11:58PM
945
July 28, 2016 09:14AM
907
July 29, 2016 05:11AM
914
July 29, 2016 01:10PM
919
July 29, 2016 06:58PM
895
August 02, 2016 05:48AM
Re: Wrong estimation of Rows in explain
937
August 02, 2016 06:23PM
897
August 02, 2016 05:38AM
896
August 04, 2016 05:31AM
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.