Author Archives: zardosht

Better Primary Keys, a Benefit to TokuDB’s...

Posted on by zardosht

In our last post, Bradley described how auto increment works in TokuDB. In this post, I explain one of our implementation’s big benefits, the ability to combine better primary keys with clustered primary keys.

In working with customers,…

1 Comment

A Second Rule of Thumb for Choosing Column Order...

Posted on by zardosht

A couple of weeks ago, Baron Schwartz wrote an interesting post describing a rule of thumb he sometimes uses to choose the order of columns in an index. In a nutshell, he recommends putting highly selective columns first.…

1 Comment

MySQL 5.1 Grammar Changes to Support Clustering...

Posted on by zardosht

This post is for storage engine developers that may be interested in implementing multiple clustering keys.

After blogging about TokuDB’s multiple clustering indexes feature, Baron Schwartz suggested we contribute the patch to allow other storage engine to…

Leave a comment

How clustering indexes sometimes help UPDATE and...

Posted on by zardosht

I recently posted a blog entry on clustering indexes, which are good for speeding up queries. Eric Day brought up the concern that clustering indexes might degrade update performance. This is often true, since any update will…

Leave a comment

Clustering indexes vs. Covering indexes

Posted on by zardosht

Yesterday, I (Zardosht) posted an entry introducing clustering indexes. Here, I elaborate on three differences between a clustering index and a covering index:

Clustering indexes can create indexes that would otherwise bounce up against the limits on the maximum…

6 Comments

Introducing Multiple Clustering Indexes

Posted on by zardosht

In this posting I’ll describe TokuDB’s multiple clustering index feature. (This posting is by Zardosht.)

In general (not just for TokuDB) a clustered index or a clustering index is an index that stores the all of the data for…

15 Comments