Spil Games hackday At Spil Games we organise a monthly hackday
(actually the last two Thursday/Friday of the month) where
several teams try to hack something in limited amount of time.
The only rules for the hackday are: make something cool, keep it
simple, document it, learn something and have fun. In
general it means time is […]

I have a difficult task of making this post interesting, helpful
and personal at the same time. I think the main goal is to
balance these aspects, and I really appreciate your comments and
suggestions that I will add here.

MariaDB Galera Cluster involves more effort and resource to
administer than standalone MariaDB systems. If you would like to
learn how to better manage your MariaDB cluster, then this
webinar series is for you.

We will give you practical advice on how to introduce clusters
into your MariaDB / MySQL environment, automate deployment
and make it easier for operational staff to manage and monitor
the cluster using ClusterControl.

Out of the mere 13 bugs, most were benign, but I thought there
were two worth mentioning (just because one is a slight
performance improvement for InnoDB, and the other relates to
slave consistency, so always important to see if it could affect
you):

InnoDB: For each insert, memset would be called three
times to allocate memory for system fields. To reduce CPU
usage, the three memset calls are now combined into a single
call. (Bug #17858679, Bug #71014)

And mention of MariaDB replacing MySQL as the default
implementation is referenced in their release notes here.

The full change log entry reads:

MariaDB 5.5

MariaDB is the default implementation of MySQL in Red Hat
Enterprise Linux 7. MariaDB is a community-developed fork of the
MySQL database project, and provides a replacement for MySQL.
MariaDB preserves API and ABI compatibility with MySQL and adds …

Have you ever wondered exactly does log_warnings=2 log? Well, I
have, and finally decided to check the code. (The manual used to
mention setting this to 2 for diagnosing some connection-related
problems, but I didn’t run into that comment in my most recent
search.)

Basically, in recent 5.6 source code, we find “log_warnings >
1″ in 7 files. In 5.5 source, it is only in 5 files. Here are the
7 files in 5.6:

Long story short, the main (most common) ones are when a filesort
fails (filesort.cc) or a failed login occurs (sql_acl.cc). Then
there are some replication-specific instances where it logs extra
info, such as master/slave/binlog info, “ignored” errors, and
some summary …

Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.