Home |  MySQL Buzz |  FAQ |  Feeds |  Submit your blog feed |  Feedback |  Archive |  Aggregate feed RSS 2.0 English Deutsch Español Français Italiano 日本語 Русский Português 中文
Showing entries 1 to 30 of 32819 Next 30 Older Entries
Percona Server 5.1.73-14.12 is now available
+0 Vote Up -0Vote Down

Percona Server version 5.1.73-14.12

Percona is glad to announce the release of Percona Server 5.1.73-14.12 on July 31st, 2014 (Downloads are available here and from the Percona Software Repositories). Based on MySQL 5.1.73, including all the bug fixes in it, Percona Server 5.1.73-14.12 is now the current stable release in

  [Read more...]
Testing MySQL repository packages: how we make sure they work for you
Employee_Team +2 Vote Up -0Vote Down
Around nine months ago, we launched the MySQL yum repositories for Enterprise Linux and Fedora, followed by apt repos for Debian and Ubuntu back in May. We’re extremely happy that the repos have proved to be a big hit with the community: the monthly number of downloads hit 100K recently and it is still growing […]
Testing that all projects need
+1 Vote Up -0Vote Down

Today, I was reminded of a Jim Starkey quote on the Random Query Generator:

“The Colonoscopy of Database Software”
- Jim Starkey

If your project does not have something that you can adapt that quote to, odds are your testing is inadequate.

MySQL Community Server 5.6
+17 Vote Up -0Vote Down
MySQL Community Server 5.6 (5.6.20 GA, published on Thursday, 31 Jul 2014)
Connector/C++ 1.1
+2 Vote Up -0Vote Down
Connector/C++ 1.1 (1.1.4 GA, published on Thursday, 31 Jul 2014)
MySQL Installer 5.5
+1 Vote Up -0Vote Down
MySQL Installer 5.5 (5.5.39 GA, published on Thursday, 31 Jul 2014)
MySQL Utilities 1.4
+0 Vote Up -0Vote Down
MySQL Utilities 1.4 (1.4.4 GA, published on Thursday, 31 Jul 2014)
Compare and Synchronize with Updated Comparison Tools!
+0 Vote Up -0Vote Down

We are happy to announce the update of comparison tools for Oracle and MySQL databases. Each of them has its own features that our team implemented to let you feel a professional in comparing and synchronizing databases. Choose the right product that is suited for you and enjoy your work.

Compare and Synchronize with Updated Comparison Tools!
+0 Vote Up -0Vote Down

We are happy to announce the update of comparison tools for Oracle and MySQL databases. Each of them has its own features that our team implemented to let you feel a professional in comparing and synchronizing databases. Choose the right product that is suited for you and enjoy your work.

Beyond the FRM: ideas for a native MySQL Data Dictionary
Employee +4 Vote Up -0Vote Down

The frm file has provided long service since the earliest days of MySQL. Now, it is time to replace it with a native InnoDB-based Data Dictionary.

This is a change that has been on our wish list for a long time, as well as others in the MySQL development community:

  [Read more...]
Resetting advanced options to defaults in MySQL for Excel
Employee +1 Vote Up -0Vote Down

Welcome to another blog post from the MySQL for Excel Team. Today we're going to talk about a new feature included since 1.3.0, remember you can always install the latest GA or maintenance version using the MySQL Installer also you can download directly any GA or non-GA version from the MySQL Developer Zone.

In this post we will learn how to reset several advanced options to their default values.

Remember that your feedback is very important for us, please drop us a message with your comments, suggestions for this or other

  [Read more...]
Examining the TokuDB MySQL storage engine file structure
+1 Vote Up -0Vote Down

As we know different storage engines in MySQL have different file structures. Every table in MySQL 5.6 must have a .frm file in the database directory matching the table name. But where the rest of the data resides depends on the storage engine.

For MyISAM we have .MYI and .MYD files in the database directory (unless special settings are in place); for InnoDB we might have data stored in the single table space (typically ibdata1 in the database directory) or as file per table (or better said file per partition) producing a single file with .ibd extension for each table/partition. TokuDB as of this version (7.1.7) has its own innovative approach to storing the table contents.

I have created the table in the database test having the following

  [Read more...]
Chicago MySQL Meetup August 4th
Employee +1 Vote Up -0Vote Down

High Availability With MySQL – Jay Janssen of Percona

Monday, August 4, 2014
6:00 PM

111 W. Washington St.
Suite 2100
Chicago, IL

Come join Jay Janssen, Principal Consultant at Percona as he speaks about High Availability with MySQL. Jay has been with Percona since 2011. Before that, spent 7 years working for Yahoo in a variety of fields including High Availability architectures, MySQL training, tool building, global server load balancing, multi-datacenter environments, operationalization, and monitoring.

Pizza and beverages will be provided.

  [Read more...]
Using innodb_large_prefix to avoid ERROR 1071
+2 Vote Up -0Vote Down

If you've ever tried to add an index that includes a long varchar column to an InnoDB table in MySQL, you may have seen this error:

ERROR 1071 (42000): Specified key was too long; max key length is 767 bytes

The character limit depends on the character set you use. For example if you use latin1 then the largest column you can index is varchar(767), but if you use utf8 then the limit is varchar(255). There is also a separate 3072 byte limit per index. The 767 byte limit is per column, so you can include multiple columns (each 767 bytes or smaller) up to 3072 total bytes per index, but no column longer than 767 bytes. (MyISAM is a little different. It has a 1000 byte index length limit, but no separate column length limit within that).

One workaround for these limits is to

  [Read more...]
Early Bird Pricing for MySQL Central @ Oracle Open World Extended to August 1st
Employee +1 Vote Up -1Vote Down

Register before August 1st for early bird pricing!

Millions of organizations around the world trust MySQL to power their business-critical web, cloud, and embedded applications. Want to learn best practices to develop next-generation applications with MySQL? Joins us at MySQL Central @ OpenWorld.

Learn new skills
Share and network with the global MySQL community
Hear about new MySQL features directly from Oracle
Get insight on product roadmaps
Have fun

OSCON 2014: Wrap Up
+0 Vote Up -0Vote Down
Tue, 2014-07-29 19:36Marc Sherwood

Another OSCON has been wrapped up. While these year was slightly smaller than last year it was still an amazing event. The interesting part was that MySQL and MariaDB seemed to be bigger topics than in years gone by.

Now that I have been back in the office for a few days, I am getting caught up on my overloaded inbox, and have had some time to reflect on the event.

The first thing that comes to mind is that MariaDB adoption rate is growing rapidly, and we hear about more amazing deployments at each event we attend. This year we met with a number of people who have made the switch from MySQL to MariaDB for their corporate use, as well as a good number of hosting companies who have migrated to MariaDB. We are working on getting some of these stories ready to share so stay tuned for more on that!

We aim to have fun in the MariaDB booth - how else could we

  [Read more...]
Prevent MySQL downtime: Set max_user_connections
+1 Vote Up -0Vote Down

One of the common causes of downtime with MySQL is running out of connections. Have you ever seen this error? “ERROR 1040 (00000): Too many connections.” If you’re working with MySQL long enough you surely have. This is quite a nasty error as it might cause complete downtime… transient errors with successful transactions mixed with failing ones as well as only some processes stopping to run properly causing various kinds of effects if not monitored properly.

There are number of causes for running out of connections, the most common ones involving when the Web/App server is creating unexpectedly large numbers of connections due to a miss-configuration or some script/application leaking connections or creating too many connections in error.

The solution I see some people employ is just to increase

  [Read more...]
MySQL Cluster latest developments – webinar replay + Q&A
Employee +2 Vote Up -0Vote Down

I recently hosted hosting a webinar which explained what MySQL Clusrter is, what it can deliver and what the latest developments were. The “Discover the latest MySQL Cluster Developments” webinar is now available to view here (http://www.mysql.com/news-and-events/web-seminars/discover-the-latest-mysql-cluster-developments/" target="_blank). At the end of this article you’ll find a full transcript of the Q&A from the live session.


View this webinar to learn how MySQL Cluster 7.3, the latest GA release, enables developer agility by

  [Read more...]
Orchestrator 1.0.4 released
+1 Vote Up -0Vote Down

Outbrain's orchestrator Version 1.0.4 is released.

Quick links: Orchestrator Manual, FAQ, Downloads

What's new?


orchestrator now does a much better visualization of Master-Master replication:

  [Read more...]
MaxScale, from proxy to replication relay. Part 2, the slave side
+0 Vote Up -0Vote Down
Tue, 2014-07-29 10:00mriddoch

Part 1 of this blog post told the story of creating a binlog router for MaxScale that could connect to a MySQL Replication Master, download the binlog file from that master and store them locally on the MaxScale server. This post will concentrate on the other side of the router, the interaction with the MySQL slaves that will see MaxScale as the replication master.

Router Structure

In some ways the role of master for MaxScale is much closer to the more expected style of interaction that MaxScale was designed to deliver; a connection originates from a client to a MaxScale service. MaxScale then processes that requirement and returns a result back to the client. The most obvious difference is of course that the processing does not involve

  [Read more...]
Galera Cluster using GTID: MySQL vs. MariaDB
+0 Vote Up -0Vote Down

Using GTID to attach an asynchronous Slave sounds promising. Lets have a look at the two existing GTID implementations and their integration with Galera.


There is one GTID used by the cluster and every node increments the common seqno by itself. This works well as long all transactions are replicated by Galera (simplified InnoDB). Because Galera takes care of the Commit Order of the transactions on all nodes. So having identical GTID/seqno from the start there are no problems.

  node1> show global variables like 'gtid_binlog_pos';
  | Variable_name   | Value   |
  | gtid_binlog_pos | 0-1-504 |

  node2> show global variables like 'gtid_binlog_pos';
  [Read more...]
Replacing pt-slave-delay with MASTER_DELAY in MySQL 5.6
+1 Vote Up -0Vote Down

In the past I have used pt-slave-delay when I want to maintain an intentionally delayed replica. Now that I have upgraded to MySQL 5.6 I am switching over to use MASTER_DELAY, which is a built-in feature that does the same thing.

For example I can replace this:

``` pt-slave-delay --delay 7d --interval 1m --daemonize


With this:


The implementation is similar: the IO thread copies the events to the relay log as fast as normal, but the SQL thread only executes events older than the defined lag. The process to

  [Read more...]
Getting Started with the MariaDB HandlerSocket Plugin
+0 Vote Up -0Vote Down
Mon, 2014-07-28 13:52adonnison

About 4 years ago, the guys at DeNA created the HandlerSocket plugin for MySQL. In Yoshinori Matsunobu's blog, he benchmarks HandlerSocket as more than 7 times the throughput of using the standard libmysql, and nearly twice that of a memcache front end.

So what is HandlerSocket? It is a plugin that bypasses the SQL layer and therefore misses out on the overhead required to parse the SQL. This does mean that you don't have access to SQL statements, but it does provide CRUD (Create, Read, Update, Delete) operations that effectively gives you a NoSQL access to your database.

HandlerSocket, when started, creates a set of listener processes that wait for connections. Two

  [Read more...]
MariadB Galera: Attaching an asynchronous Slave using GTID
+0 Vote Up -0Vote Down

Galera the synchronous Master-Master replication is quite popular. It is used by Percona XtraDB Cluster, MariaDB Galera Cluster and even patched MySQL binaries exist. Quite often you want to add a slave to a Galera Cluster. This is going to work quite well. All you need is at least configure log_bin, log_slave_updates and server_id on the designated Masters and attach your Slave.


Even you can use traditional (non GTID) replication. Using non GTID replication is a hassle. As you need to search for the right offset on the new Master to attach your Slave on.

Using GTID promises to be easier. As you simply switch to the new Master and the replication framework finds the new position based on the GTiD automatically.

As a fact we have two GTID

  [Read more...]
What I learned while migrating a customer MySQL installation to Amazon RDS
+1 Vote Up -0Vote Down

Hi, I recently had the experience of assisting with a migration of a customer MySQL installation to Amazon RDS (Relational Database Service). Amazon RDS is a great platform for hosting your MySQL installation and offers the following list of pros and cons:

  • You can scale your CPU, IOPS, and storage space separately by using Amazon RDS. Otherwise you need to take downtime and upgrade physical components of a rack-mounted server.
  • Backups, software version patching, failure detection, and (some) recovery is automated with Amazon RDS.
  • You lose shell access to your DB instance
  • You lose SUPER privilege for regular users. Many SUPER-type statements and commands are provided for as a Stored Procedure.
  • It is easy to set up multiple read
  [Read more...]
Multisource Replication: How to resolve the schema name conflicts
+0 Vote Up -0Vote Down
Mon, 2014-07-28 10:22claudionanni

MariaDB 10.0 has introduced the functionality to replicate data from more than one Master server. This is what many have been waiting for, especially those who do business intelligence analysis, aggregation and reporting on data coming from different and sometimes related applications.

The way multi-source replication is implemented is extremely simple - for every Master you need what is called a 'connection'. Previously you just had one, the default. Each 'connection' points to a Master and it has, just like regular replication, two threads: IO Thread and SQL Thread. This means that if you have two different Masters using the same Schema name, the two 'connections' associated with the separate Masters would operate on the same Schema on the Slave (specifically the Slave SQL Thread of both connections would work in the same

  [Read more...]
Some MySQL security tips
+1 Vote Up -0Vote Down

This is a brief list of security tips for MySQL. It is by no means complete.

  • Follow the sudo example. Don't let all you DBAs and Ops have the password for the root account. Have each and every one of them have their own personal super-duper account, with their own personal and private password. This makes it so easy when someone leaves the company. No need to change passwords, just to remove the employee's account.
  • Block root. Either remove it completely or forbid it from logging in. Yes, there's a way hack in MySQL to have a valid account blocked from logging in. One way of making this happen is via common_schema's sql_accounts. Here's how to block root account using common_schema:
  [Read more...]
Prewarm your EBS backed EC2 MySQL slaves
+1 Vote Up -0Vote Down

This is the story of cold blocks and mismatched instances and how they will cause you pain and cost you money until you understand why.

Most of the clients that we support run on the Amazon cloud using either RDS or running MySQL on plain EC2 instances using (Provisioned IOPS) PIOPS EBS for data storage.

As expected the common architecture is running a master with one or more slaves handling the read traffic.

A common problem is that after the slaves are provisioned (normally created from an EBS snapshot) they lag badly due to slow IO performance.

Unfortunately what tends to be lost in the “speed of provisioning new resources” fetish is some limitations in terms of data persistence layer (EBS).

If you are using EBS and you have created the EBS volume from snapshot or created a new volume you have to pre-warm the EBS volume

  [Read more...]
What Privileges Does EXPLAIN Require in MySQL?
+0 Vote Up -0Vote Down

Here's a simple question that I wasn't able to solve with Google or the MySQL documentation (which is normally excellent). Perhaps it's mentioned somewhere, but I can't find it. Here's the question:

What privileges must a user have to run EXPLAIN for a query?

Is there an EXPLAIN privilege? No, there's not.

The answer turns out to be really simple: you need the same privileges that you'd need to execute the query itself. At least, as far as I know, that's the case. I haven't been able to find a counter-example, and from what I know of the MySQL query execution process, this makes perfect sense.

If you're not familiar with how EXPLAIN works, it's roughly

  [Read more...]
FromDual.en: FromDual: Tools for MySQL and Galera - Backup - Monitoring - Operations
+0 Vote Up -0Vote Down
Taxonomy upgrade extras: galeraBackupmanagermonitoringOperations

FromDual tools provide valuable additional functionality which facilitate and optimize daily operations of your MySQL databases. Since our last newsletter a lot of things have changed in the FromDual tools.

To the MySQL Environment (MyEnv) numerous improvements and suggestions of our customers were added. The most important changes were introduced to the MySQL Backup Manager (mysql_bman).

  [Read more...]
Showing entries 1 to 30 of 32819 Next 30 Older Entries

Planet MySQL © 1995, 2014, Oracle Corporation and/or its affiliates   Legal Policies | Your Privacy Rights | Terms of Use

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.