MySQL Forums
Forum List  »  Optimizer & Parser

Re: suggestion for optimizing with non-matching compound indexes
Posted by: Nathan Cheng
Date: March 16, 2006 12:15PM

In my case it's because the deadletter table is about 11GB large and it doesn't get queried on the b column very often. If this was a frequent query for me, then, yes, maybe I would create the additional index. I say "maybe", because the cardinality of the front column is so small (2 or 3) that it just kind of hurts.

Options: ReplyQuote


Subject
Views
Written By
Posted
Re: suggestion for optimizing with non-matching compound indexes
2090
March 16, 2006 12:15PM


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.