MySQL :: Re: No other way than delete primary key to create partitions by single datetime columns?

New Topic

Re: No other way than delete primary key to create partitions by single datetime columns?

Posted by: Rick James
Date: August 24, 2015 12:36PM

An INDEX is unlikely to be "more powerful after the table is partitioned". A tiny advantage is that the BTree containing the index might be one level shallower. However, the pruning to pick the partition cost something -- probably as much as the BTree saves!

My blog contains the only 4 use cases I have found where PARTITIONing improves performance:
http://mysql.rjweb.org/doc.php/partitionmaint

Navigate: Previous Message• Next Message

Options: Reply• Quote

Subject

Views

Written By

Posted

No other way than delete primary key to create partitions by single datetime columns?

2609

Sam Young

August 20, 2015 08:00PM

Re: No other way than delete primary key to create partitions by single datetime columns?

1629

Jonathan Stephens

August 21, 2015 02:53AM

Re: No other way than delete primary key to create partitions by single datetime columns?

1494

Sam Young

August 23, 2015 08:57PM

Re: No other way than delete primary key to create partitions by single datetime columns?

1525

Rick James

August 22, 2015 03:35PM

Re: No other way than delete primary key to create partitions by single datetime columns?

1480

Sam Young

August 23, 2015 09:23PM

Re: No other way than delete primary key to create partitions by single datetime columns?

1523

Rick James

August 24, 2015 12:36PM

Re: No other way than delete primary key to create partitions by single datetime columns?

1594

Sam Young

August 26, 2015 12:53AM

Re: No other way than delete primary key to create partitions by single datetime columns?

1502

Rick James

August 26, 2015 10:02AM

Re: No other way than delete primary key to create partitions by single datetime columns?

1464

Sam Young

August 26, 2015 07:42PM

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.