MySQL Forums
Forum List  »  Optimizer & Parser

Re: suggestion for optimizing with non-matching compound indexes
Posted by: Harrison Fisk
Date: March 16, 2006 11:40AM


This does exist in other databases (at least Oracle that I know of, not sure about others), and is called index skip scans. Read more at for example.

The issue with doing a skip index scan is that the usefulness is directly dependant on the cardinality of the front column. Most of the time the most selective column is the first one, so this doesn't work out very well in many cases.

Also a skip scan is always going to be slower than a regular index lookup. In your example, why wouldn't you add another index just on the b column? Even if a skip index scan was possible, it will be more efficient to add an index on b.

With that said, there are, of course, possible cases where this could be useful. I do believe this is on the TODO list, however I don't believe it is near the top.

Options: ReplyQuote

Written By
Re: suggestion for optimizing with non-matching compound indexes
March 16, 2006 11:40AM

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.