Like TokuDB, InfiniDB is now a fully open source server product. In the past infiniDB was “almost open source”. The open source version was an old release with no access to the advance functions like MPP multi-server execution. This is no more the case. With InfiniDB 4 the open source version is the latest release [...]

I often find myself in conversations with long time MySQL users who tell me about little annoyances in MySQL that make the product harder to use. Sometimes these annoyances can stay in a product for seemingly forever, because they require a change in behaviour (breaking backwards compatibility) or they are the result of architectural limitations not easily fixed.

In either case, I think it’s important to commend the MySQL engineering team at Oracle, because as well introducing a number of big ticket features for MySQL 5.6, they actually invested a lot of time into closing out a lot of old bugs.

Here is my list of historical gripes, now resolved:

1. innodb-file-per-table ON by default means it is easier to reclaim space caused by run-away tables.
2. When you change innodb_log_file_size in configuration, InnoDB will now resize logs to match automatically. …

As noted in earlier posts, exams for the MySQL 5.6 Developer and DBA certifications are entering a beta period, allowing candidates to register for the exams at steep discounts from normal certification exam fees.  I’ve registered to take both exams late this month, and – like Moritz – I’m starting to prepare for the exams now.  For those considering sitting for the exams, my plan is to document my exam preparation in a series of blog entries.  This won’t be a formal or official study guide, but I hope it will prove useful to those preparing for …

Saw this on @awsmarketplace the other day:

#opensource #MariaDB by @SkySQL on @AWSMarketplace http://t.co/o3KQ9xe9sr #mysql

— AWS Marketplace (@awsmarketplace) October 8, 2013

Now on the AWS Marketplace, you can …

Percona XtraDB Cluster (PXC) itself manages quorum and node failure.  Minorities of nodes in a network partition situation will move themselves into a Non-primary state and not allow any DB activity.  Nodes in such a state will be easily detectable via SHOW GLOBAL STATUS variables.

It’s common to use HAproxy with PXC for load balancing purposes, but what if you are planning to just send …

5.6.Debian

Installing MySQL 5.6 using the package provided via dev.mysql.com is some kind of silly.
Using a package you expect the packagemanager to solve conflicts and dependencies and you expect to have a running application after install.But ..
I downloaded the Debian Package.

root@debianmy56:/var/tmp# dpkg -i mysql.deb 
Selecting previously deselected package mysql.
(Reading database ... 8799 files and directories currently installed.)
Unpacking mysql (from mysql.deb) ...
Setting up mysql (5.6.14) ...

Ok - beside the unusual name for the package - everything worked fine. Lets see if we got mysql user and group:

root@debianmy56:/var/tmp# getent passwd mysql
root@debianmy56:/var/tmp# getent group mysql

Oha, is there an init-script?

root@debianmy56:/var/tmp# ls /etc/init.d/| grep -i mysql

Ok thats consequent and of …

…

Done is better than perfect. That is one of Spil Games Engineering’s principles and it is really something I embrace. Almost one and a half year ago, Engineering started to use StatsD and Graphite for collecting and graphing performance metrics and one year ago I got fed up that there was, except for a couple of […]

The post MySQL StatsD project on Github appeared first on Spil Games Engineering.

Today we released TokuDB v7.1, which includes the following important features and fixes:

• Added ability for users to view lock information via information_schema.tokudb_trx, information_schema.tokudb_locks, and information_schema.tokudb_lock_waits tables.
• Changed the default compression to zlib and default basement node size to 64K.
• Changed default analyze time to 5 seconds.
• Added server variable to control amount of memory allocated for each bulk loader. In prior TokuDB versions each loader allocated 50% of the available TokuDB cache.
• Changed table close behavior such that all data for the table remains in the cache (and is not flushed immediately).
• Removed user reported stalls due to cache pressure induced by the bulk loader, lock tree escalation, and a particular open table stall.
• Several bugs and behavioral issues reported by users. …

It's no secret that you shouldn't rely on replication filtering. Recently a customer asked if an `ON DELETE CASCADE` would still affect the data on a slave if the table was being ignored through replication filtering. It was one of those occasions that I couldn't give a confident answer without a quick test but alas the gut was right and the obvious answer is yes, "ON DELETE|UPDATE CASCADE" will change data even if you replicate using replication filters.

I tested using RBR and SBR. If anything I was questioning the behaviour of RBR here but it turns out to be consistent with SBR. I had a master-slave setup already deployed for some other testing so it was easy to implement the FKs needed for this. The dataset is the trusty world db available from dev.mysql.com and I needed to change the constraints on the table to match the conditions proposed.
Master …