MySQL Forums
Forum List  »  Partitioning

Re: How to handle secondary keys in partitioning?
Posted by: Rick James
Date: May 06, 2010 12:04AM

A couple of follow on questions for Mattias:

For a non-Partition table, "where sender_id=1 ordered by date" together with "INDEX(sender_id, date)" will (I think) avoid a filesort. Seems like in a Partitioned table, each partition could deliver the rows in order, and then the priority queue could put them together. Or is that asking for more smarts than is in Partitioning today? (I note that you said "and there will be an additional sorting cost".)

"the cost for index writes should be lower for partitioned tables, since the b-tree depth is lower per partition than it would be for a non partitioned table" -- isn't that offset by the effort to figure out which Partition to reach into?

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.