MySQL lets database administrators define access rights on many levels – from the ability to run global commands down to access to individual columns. Some rights can be applied to many different objects, such as for example SELECT or UPDATE, which can be granted globally or restricted only to certain databases or tables, while others are only meant for one specific purpose. An example of the latter could be FILE privilege, which permits user to interact with the file system from inside a database instance. It only makes sense as the global right and not anywhere else.

As any other activity that produces changes, GRANT statements are replicated to MySQL slaves. Regardless of the binary log format setting, such events are always logged in STATEMENT format. It is likely because the command needs to handle more than just updating the contents of a few system tables, so such design allows each slave to fully execute the changes within their …

If T.S. Eliot were a MySQL DBA, I think he would have been more upbeat about April.

We are gearing up for an incredible second half of April. We will be presenting three separate sessions at the Percona Live: MySQL Conference and Expo 2013, April 22-25, in Santa Clara, CA. In addition, we will be presenting at SkySQL’s MySQL & Cloud Database Solutions Day on Friday, April 26 at the same location.

Come by to see us in Booth #114, or stop by one of our sessions:

Using TokuDB: A Guided Walk Through a …

Just a reminder for 2 important MySQL events as they have already been announced:

MySQL Community Reception - “Let’s Celebrate MySQL 5.6 GA!”

• Date: Apr 22, 2013
  
• Place: TechMart Santa Clara,  5201 Great America Parkway,  Santa Clara,  CA 95054
• See the whole announcement here;
• More information and registration is available here.
  

MySQL Connect CfP is open by April 12, 2013.

• Date: Sep 21-23, 2013
• Place: SFO, US
  
• See the whole announcement …

This post is about keeping it simple when it comes to managing a company’s databases. Simplicity lets me easily diagnose problems, quickly setup new databases, readily validate my actions while configuring replication, and identify the right course of action even at two in the morning.

Simplicity in my infrastructure allows me to diagnose problems. It is difficult to diagnose if a past network spike was from a Memcached instance or a Postfix instance hosted on the same machine. Service segregation, meaning leaving a single host responsible for a single heavy process, significantly aids in diagnoses because standard, rapidly deployed graphs in any of a number of RRDTool implementations can show host-wide performance statistics that can only have come from the single heavy process that machine is responsible for running.

Simplicity in my instance configuration has made it easy to add another instance. The current time from request …

Team MariaDB will be at the Percona Live MySQL Conference & Expo 2013, held in Santa Clara from April 22-25 2013. We will also be at the SkySQL Solutions Day held on April 26 2013 at the same venue, the Hyatt Santa Clara. We have talks, a booth in the DotOrg Pavilion, have a BoF and we’re participating in the passport program.

Team MariaDB talks:

1. (Monday) Advanced Query Optimizer Tuning & Analysis, a tutorial by Sergei Petrunia & Timour Katchaounov
2. (Tuesday)  …

During the process of researching InnoDB’s storage formats and building the innodb_ruby and innodb_diagrams projects discussed in my series of InnoDB blog posts, Davi Arnaut and I found a number of InnoDB bugs. I thought I’d bring up a few of them, as they are fairly interesting.

These bugs were largely discoverable due to the innodb_space utility making important internal information visible in a way that it had never been visible in the past. Using it to examine production tables provided many leads to go on to find the bugs responsible. When we initially looked at a graphical plot of free space by page produced from innodb_space data, we were quite surprised to see so many …

We are working towards connecting with the MySQL user community in Bangalore. Please join us on the facebook group MySQL User Camp to get updates on upcoming activities

The first meet was held @ Oracle, Kalyani Magnum on March 22nd. Sanjay Manwani and Karthik P R have blogged about it

http://remotemysqldba.blogspot.in/2013/03/bangalore-mysql-user-camp.html
…

MySQL has always given great emphasis on quality.  This has got even better in the last few years with increased investment in the dedicated test team. The Server test team tripled in size during 5.6 development and all 5.6 features have undergone thorough testing at the hands of the QA team.
I have more than 15 years experience in this industry and have worked on different products and technologies as part of test and development teams. Compared to most others I find the developers in MySQL very involved in testing. Here the developers are expected to write functional tests for their features and bug fixes. This is how it was historically and this continues today in spite of the bigger test team. This model has the following advantages

• Code is in reasonably good shape when delivered to test team
• Testers can focus on more complex tests since the straightforward tests will be written by the developers …

Annnnnd here’s the recording:

Hey all!

The Percona Live MySQL Conference and Expo is coming up in 2 weeks, meaning the last of preparations are under way. In the meantime, #DBHangOps is coming your way on Wednesday at 12:00pm PDT (19:00 GMT) with:

• Talk about Performance Schema from Mark Leith
• Some discussion on how people use and manage MySQL slow query logs in their environments
• Filesystems and MySQL — which do you use, why, and how
• What you’re excited about at Percona Live!

As always, hit up this twitter search or this blog post to grab the google hangout link to join!

See y’all on Wednesday!

Currently the English error messages are embedded in all of the tests in MySQL. This means that you can’t really update the English translations without breaking a bunch of tests. I’m not sure if there’s a standard way to fix this, but it occurs to me that it would be quite easy to have a “system” localization which just prints a language-neutral version of the error, meaning that any version of it can be updated without breaking any tests.

For example, the following simple syntax error gives a message in English:

mysql> select foo;
ERROR 1054 (42S22): Unknown column 'foo' in 'field list'

This is based on the following definition in the errmsg-utf8.txt file:

ER_BAD_FIELD_ERROR 42S22 S0022
        eng "Unknown column '%-.192s' in '%-.192s'"

In a test case this might be codified as:

--echo # Test that ER_BAD_FIELD_ERROR works.
--error ER_BAD_FIELD_ERROR
SELECT foo;

The …