Today as i was learning for the new MySQL 5.6-certification (more about that in a later post) i stumbled again across the host_cache-Table that was added to MySQL in 5.6.5. Before that you had no chance to check which hosts are already known by the MySQL-server.

So thats a pretty good feature for us. And even better: you could resize the size of the host_cache now! Whoohoo, awesome! As we have a lot of servers that need to connect to one of our MySQL-server and we could not switch to ip-based-authentication we were really happy to tune the host_cache-size without recompiling MySQL.

Unfortunately i noticed that the performance_schema.host_cache table only holds 128 rows and that the content was changing everytime i checked. So i logged in to a server that wasn’t already in the host_cache-table, made a connection attempt to the mysql server  and checked again the host_cache-table:

The server was now in the …

There is a Debian MariaDB plan from the MySQL package team. There is good news as on September 30 2013, the upload to Debian unstable is complete with MariaDB 5.5 (5.5.32). It’s now only a matter of time before this becomes available in Debian. 

Its great to see the work of Otto Kekäläinen finally make it into Debian. I would say this has been in the works for seven months. Much thanks to James Page (Canonical) and Clint Byrum (HP, Debian Developer) for reviewing and uploading.

This joins the …

To bring to attention those who will be in Tokyo, Japan or Buenos Aires, Argentina:

1. MariaDB/MySQL Community Event – 9 October 2013 – Tokyo, Japan. Come see Michael Carney, Ivan Zoratti, Kentoku Shiba (creator of the SPIDER storage engine) and Colin Charles at this event. It is from 12.30pm – 8pm, and includes evening cocktails to some extent. It should be free to attend.
2. MySQL NoSQL Cloud – 15-16 October 2013 – Buenos Aires, Argentina. This is the second such conference happening in Buenos Aires, and this time there are plenty of speakers who didn’t make it around the first time. Cost is nominal.

Related posts:

1. …

I just wanted to collect the links of the Google and MariaDB relationship. These were all items in September 2013.

The Register: Google swaps out MySQL, moves to MariaDB – this was largely based on a presentation at SLAC by Jeremy Cole (slides). Same news was picked up by ReadWrite (with a different angle naturally), Google Waves Goodbye To MySQL In Favor Of MariaDB.

If you’re more audio inclined, there was great discussion on the This Week in Google podcast: checkout episode …

One of our customers reported that ‘create table select from’ statements stall for a period of time equal to the TokuDB lock timeout.  This indicated a lock conflict between multiple transactions.  In addition, other MySQL clients that were opening unrelated tables were also stalled.  This indicated that some shared mutex is held too long.  We discuss details about this bug and how it was fixed.  The bug fix will be distributed in TokuDB 7.1.0.

Example
Suppose that we set the tokudb lock timeout to 60 seconds just to exaggerate the stall.

mysql> set global tokudb_lock_timeout=60000;
Query OK, 0 rows affected (0.00 sec)


We then create a simple table.

mysql> create table s (id int primary key);
Query OK, 0 rows affected (0.02 sec)


When we create new table (t) and populate it from some …

Save Time & Money – Do It Right The First Time

SPEAKER: Gerry Narvaja, Tokutek
DATE: Tuesday, October 8th
TIME: 1pm ET

If you are thinking of using the leading open source database in a project, learn just how easy it is to get started with MySQL, and how important it is to do it right. A few simple decisions early in development, and knowing when and how to effectively use the TokuDB performance engine, can save significant time and money down the road. Key metrics for MySQL success include performance, scalability, database size, and agility. Register Now!

Attend this webinar to learn:

• The basics of installing and configuring MySQL and TokuDB
• How to maximize performance for long-term scalability
• How to configure compression for highest ROI
…

Reposted from Monty Says.

I recently read some comments that we at the MariaDB Foundation have not been very open about what we are doing.

We are very sorry about this. The problem is not that we are secret about what we are doing, the problem is that not many of us working at the MariaDB Foundation are very active bloggers.

I will try to address this concern by starting a monthly blog about the MariaDB development that MariaDB Foundation employees are doing. This together with Simon Phipps’ state of the sea lion blog, which is published here, should hopefully give everyone a better idea of what we are doing.

At the MariaDB Foundation we are now 4 people …

About a month ago, I accepted an offer to work at SkySQL as the Chief Evangelist for MariaDB. So the change in affiliation announced in April 2013 has come to fruition. What this realistically means is that my email address changes to colin@mariadb.com, though I am still reachable at colin@mariadb.org even though I’m not part of the MariaDB Foundation.

There are a lot of structural changes that urgently need work and I expect to be spending quite some time on all this. In the meantime, read an update from the SkySQL CEO Patrik Sallner.

…

October 1, 2013 By Severalnines

Database vendors regularly issue critical patch updates to address software bugs or known vulnerabilities, but for a variety of reasons, organizations are often unable to install them in a timely manner, if at all. Evidence suggests that companies are actually getting worse at patching databases, with an increased number violating compliance standards and governance policies1.

Patching that require database downtime would be of extreme concern in a 24*7 environment, however most cluster upgrades can be performed online. ClusterControl performs a rolling upgrade of the cluster, upgrading and restarting one node at a time. The logical upgrade steps might slightly differ between the different cluster types. 

Upgrading your Database

In this post, …

As I wrote in a previous post, MariaDB / MySQL has some issues with the standard UTF-8 encoding there. This UTF-8 encoding limits us to 3 UTF-8 bytes or 2 UNICODE bytes if you want to look at it that way. This is slightly limiting, but for languages it is usually pretty much OK, although there are some little used languages in the 3 byte UNICODE range. But in addition to languages, you will be missing symbols, such as smileys!

Help is on the way though, in the utf8mb4 character set that is part of both MariaDB and MySQL. This is a character set that is just like the one just called utf8, except this one accepts all the UNICODE characters with up to 3 UNICODE bytes, or 4 bytes using the UTF-8 encoding.

This means that there are more limits to how long a column might be when using utf8mb4 compared …