In December 2015, MariaDB Evangelist Colin Charles was asked to present on MariaDB Security and Encryption at the London MySQL Meetup group. This blog is a summary of Colin’s presentation.
Customers have been excited to get their hands on the performance and maintenance enhancements and data encryption capabilities made available through MariaDB 10.1. We are happy to announce that MariaDB Enterprise and Enterprise Cluster subscriptions now support MariaDB 10.1 and make all of these features available to our subscription customers.
Several months ago, I wrote a blog post about configuring PAM authentication and user mapping in MariaDB. While it is useful to map a system user account to a MariaDB user account, a lot of users actually wanted to be able to map all system users in a particular system group to the same MariaDB user account without mapping the system accounts individually.
We are pleased to announce that MaxScale 1.3.0 beta is now open for the community. Read our blog regarding the latest new features, and where to find the release notes.
Having written the Building MaxScale from source on Centos7 tutorial, we have received requests about writing one for Ubuntu. It seems the most mentioned version is the 14.04 LTS version so we’re going to go with that. For the purpose of this tutorial, I’ve installed a fresh installation of Ubuntu 14.04.3 LTS (Trusty Tahr) on a VM.
MaxScale is a bit more complicated to build on Ubuntu and Debian, but should still be something almost everyone can do.
We’ve gotten a few questions on detailed installation tutorials for specific systems. So I decided to write one for CentOS 7 which is a pretty common OS. For this I’m using a fresh installation of CentOS 7 on a virtual machine.
In this blog we look at how MaxScale helps minimize database access down time for client applications. Following our partner Severalnines’ recent announcement we want to inform the MariaDB community know that there is an automation and management platform available to them, ClusterControl, that will help them deploy and manage MaxScale for MariaDB (which in turn also helps minimize downtime).
Losing temporary tables on a slave when
binlog_format is not set to
ROW is a well-known problem, and there is even a way to avoid it, as described by the safe slave shutdown procedure in the MySQL documentation. However, the documentation doesn't describe how to fix your slave if you accidentally shut it down while it has temporary tables open. In this blog post, I'll describe how to do that.
The year has flown by so quickly and I am simply stunned that Fall is now upon us. With the changing of seasons it is time for another software release of MariaDB Enterprise (MDBE) as well as MaxScale.
My last row-level security blog post got a few questions, so I decided that it would be good to follow up with more detail. The last blog post described some basic information about row-level security, but row-level security policies are highly dependent on an application's or organization's security requirements. In this blog post, I'm going to walk through an example row-level security implementation in MariaDB 10.0 in a little more detail.