(Leo Hsu and Regina Obe) You’ll often hear the term planner statistics thrown around by database geeks. Did you update your statistics. This lingo isn’t even limited to PostgreSQL, but is part and parcel to how most decent databases work. For example in PostgreSQL you do a vacuum analyze to update y

(Vadim) This is probably the feature I missed most from early days when I started to use InnoDB instead of MyISAM. Since that I figured out how to survive without it, but this is first question I hear from customers who migrated from MyISAM to InnoDB – can I just copy .ibd files from one server to a

(Ronald Bradford) For any production MySQL Database system, running RAID is a given these days. Do you know what RAID your database is? Are you sure?. Ask for quantifiable reproducible output from your systems provider or your System Administrator.

(Baron Schwartz) As you can probably guess, I’m catching up on reading my blogs. I’ve just read with interest about TokuDB’s multiple clustering indexes. It’s kind of an obvious thought, once someone has pointed it out to you. I’ve only been around products that insist there can be Only One clustere

(Shlomi Noach) This post follows Ronald Bradford’s More Basic MySQL Security, and Lenz Grimmer’s Basic MySQL Security: Providing passwords on the command line and More on MySQL password security.

(Baron Schwartz) I wanted to share a little rule of thumb I sometimes use to decide which columns should come first in an index. This is not specific to MySQL, it’s generally applicable to any database server with b-tree indexes. And there are a bunch of subtleties, but I will also ignore those for

(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 require updating the clustering index as well.

(Lenz Grimmer) My last post about Basic MySQL Security generated a number of interesting comments, thanks for all your feedback! I’d like to address a few points that were mentioned there:

(Mikael Ronstrom) I’ve noted that one reason that InnoDB can get difficulties when there are many concurrent transactions in the MySQL Server is that the lock time of the kernel_mutex often increases linearly with the number of active transactions. One such example is in trx_assign_read_view where

In this post we’ll describe a query that accrued significant performance advantages from using a relatively long index key. (This posting is by Zardosht and Bradley.)