EmergencyEMERGENCY? Get 24/7 Help Now!

Development plans

 | September 8, 2008 |  Posted In: Percona Software

We gathered together our ideas of MySQL improvements on this page https://www.percona.com/percona-lab/dev-plan.html and we are going to implement some of them. My favorite one is – make InnoDB files .ibd (one created with –innodb-file-per-table=1) movable from one server to another, however it is sort of challenging. Probably next one patch we want to integrate is […]

Read More

Neat tricks for the MySQL command-line pager

 | June 23, 2008 |  Posted In: Insight for DBAs

How many of you use the mysql command-line client?  And did you know about the pager command you can give it?  It’s pretty useful.  It tells mysql to pipe the output of your commands through the specified program before displaying it to you. Here’s the most basic thing I can think of to do with […]

Read More

Idea: Couple of more string types

 | April 18, 2008 |  Posted In: Insight for Developers

MySQL has a lot of string data types – CHAR, VARCHAR, BLOB, TEXT, ENUM and bunch of variants such as VARBINARY but I think it is not enough 🙂 I would also like to see type HEXCHAR which would be able to store hex strings, such as those returned as MD5() and SHA1() efficiently. With […]

Read More

State of MySQL Market and will Replication live ?

 | April 9, 2008 |  Posted In: Insight for DBAs

There are interesting posts these day about future of MySQL Replication by Brian Frank and Arjen. I think it very interesting to take a look at a bit bigger picture using framework from Innovators Dilemma and Innovators Solution. I’m not going to speak about disruption and commoditisation of Database Market, leaving this for Market talks, […]

Read More

MySQL should have dynamic durability settings

 | April 8, 2008 |  Posted In: Insight for DBAs

If you’re using Innodb tables MySQL has innodb_flush_log_at_trx_commit variable which defines how durable your transactions are. If you have high durability requirements you set it to 1 and log records are pushed directly to the disk on transaction commit. If you do not bother loosing come committed transactions you can set it to 0 and […]

Read More

Enum Fields VS Varchar VS Int + Joined table: What is Faster?

 | January 24, 2008 |  Posted In: Benchmarks

Really often in customers’ application we can see a huge tables with varchar/char fields, with small sets of possible values. These are “state”, “gender”, “status”, “weapon_type”, etc, etc. Frequently we suggest to change such fields to use ENUM column type, but is it really necessary (from performance standpoint)? In this post I’d like to present […]

Read More

Using VIEW to reduce number of tables used

 | September 28, 2007 |  Posted In: Insight for Developers

Many Open Source software solutions use database per user (or set of tables per user) which starts to cause problems if it is used on massive scale (blog hosting, forum hosting etc), resulting of hundreds of thousands if not millions of tables per server which can become really inefficient. It is especially inefficient with Innodb […]

Read More