MySQL Forums
Forum List  »  Optimizer & Parser

Re: MySQL 5.1.31 -- Same query scans widely different # of rows
Posted by: Rick James
Date: April 09, 2011 01:13PM

Oops. No.

Filtering on both tables in a JOIN is usually poorly optimizable. The optimizer might be able to filter in one table, but lug around the potential rows while reaching into the other table to see if they are needed. This is especially problematical if you have ORDER BY and LIMIT (which is not your case). Jørgen, can you explain it better?

Options: ReplyQuote

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.