MySQL 5.7.4 introduces the ability to set server side execution time limits, specified in milliseconds, for top level read-only SELECT statements. This feature is introduced as part of WL#6936. It is based on a contribution submitted by Davi Arnaut with Bug#68252. Thank you, Davi!

The statement timeouts work by interrupting the execution of the statement when it takes longer than a specified number of milliseconds to complete. After the specified number of milliseconds has passed, the server aborts the individual query without affecting the larger transaction or connection contexts. The following error is then reported to the client when the query is aborted:

  1907: Query execution was …

It is our pleasure to announce MySQL presence at the OpenSource Developer Conference in Taipei, Taiwan next week. MySQL has secured 2 talks and the booth where you can meet our MySQL experts. Please mark your calendars for April 11-12, 2014, especially for following MySQL talks:

• Sharding and Scale-out Using MySQL Fabric by Ryusuke Kajiyama, the OSS specialist with over 10 years of experience in system design utilizing MySQL and Open Source solutions. His talk is scheduled for Apr 11 @ 10:20-10:50.
• MySQL Utilities by Ivan Tu, the MySQL Sales Consultant in Taipei. Ivan has Java programming background and is experienced in both, MySQL and Oracle database. His talk is scheduled for Apr 11 @ 11:50-12:20.

We are looking forward to talking to you at the OSDC next week!

The way online schema changes have historically worked with statement based replication is to create an empty table on a slave, setup triggers to capture changes to a log table, copy the old table to the new table, apply the changes from the log table and atomic rename. This process breaks when using statement based replication because triggers don’t fire on events replicated to the slave. Triggers will fire on the master and the row events for any modified tables just replicate to the slave. This makes traditional online schema change break with statement based replication.

The workaround I’ve seen a few times at the conference is to run schema changes on the master when using row based replication. This is means either significantly reducing replication capacity during a schema change or having the change run really slowly so replication can keep up. Neither of these are optimal. I would like to submit an alternate method. Rather than …

I was browsing around the Internet (don’t remember what for) and I accidentally found one cool aspect of MariaDB. There is a feedback plugin and this short post is meant to encourage you to use it!

Ok, so what it does and why should you opt-in to be spied on It takes some information about your MariaDB server including it’s usage and it will send it to the MariaDB folks. It doesn’t send private data from your database. It sends stuff like what OS are you running, what version of various plugins, how did you tweaked the default settings and also how big and how busy is your server. Now a short list of why I turned this on:

• Why not? Doesn’t cost me anything, nothing from the data I send is secret.
• When I develop an …

A TokuDB MySQL test run with valgrind reported an uninitialized data error when writing into the TokuDB recovery log.

==1032== Syscall param write(buf) points to uninitialised byte(s)
==1032== at 0x3EFA60E4ED: ??? (in /lib64/libpthread-2.12.so)
==1032== by 0xB894038: toku_os_full_write(int, void const*, unsigned long) (file.cc:249)
==1032== by 0xB83248A: write_outbuf_to_logfile(tokulogger*, __toku_lsn*) (logger.cc:513)
==1032== by 0xB83326C: toku_logger_maybe_fsync(tokulogger*, __toku_lsn, int, bool) (logger.cc:836)
==1032== by 0xB8327DE: toku_logger_fsync_if_lsn_not_fsynced(tokulogger*, __toku_lsn) (logger.cc:586)
==1032== by 0xB8493E6: toku_txn_maybe_fsync_log(tokulogger*, __toku_lsn, bool) (txn.cc:600)
==1032== by 0xB7B4EBB: toku_txn_commit(__toku_db_txn*, unsigned int, void (*)(__toku_txn_progress*, void*), void*, bool, bool) (ydb_txn.cc:198)
==1032== by 0xB7B55E9: locked_txn_commit_with_progress(__toku_db_txn*, unsigned int, void (*)(__toku_txn_progress*, …

This weekend we are going to be part of the LOADays Conference (Linux Open Administration Day) a free open source event hold in Antwerp, Belgium, followed by the tutorial on Monday, April 7th.

Do not miss to attend this small but friendly event hold in Antwerp, the second biggest city in Belgium and the capital of the Antwerp province. So, you can join the sightseeing with attending LOADays and getting in touch not only with a Linux people but also with MySQL!!

MySQL is represented by our colleague Carsten Thalheimer who is going to have a talk about "Why MySQL in a Business critical environment". His talk is planned for Sunday, April 6, 2014 @ 13:30.

For the whole conference plan you can check the Schedule section of the LOADays website.

See you …

Are you already a MySQL User Group Leader?

or

Are you thinking about taking this role in the near future?

If yes, please let me invite you to the Annual User Group Leaders' Summit organized by Oracle User Group team. The purpose of this 2 days meeting is sharing the expertise, knowledge and share experience with leading the UG as well as learning of the new ways how to handle groups by using new technologies & tools (i.e. Cloud..).

It is great opportunity to talk to other User Group leaders and share the experience and knowledge with them. There will be Java User Group, Oracle User Group and of course MySQL User Group Leaders!

Find details about this event below and if you are interested and/or want to know more, please do not hesitate to contact myself or make a registration at the link below. You will be contacted by us with a …

Install Apache2, PHP5 And MySQL Support On CentOS 6.5 (LAMP)

LAMP is short for Linux, Apache, MySQL, PHP. This tutorial shows how you can install an Apache2 webserver on a CentOS 6.4 server with PHP5 support (mod_php) and MySQL support.

The MySQL Utilities Team is pleased to announce the latest release candidate (RC) release of MySQL Utilities. This release includes a number of improvements for useabilty, stability, and a few enhancements. A complete list of all improvements can be found in our release_notes.

New Utilities!
We have also included two new utilities.

• The mysqlrplsync utility was added, which checks data consistency between servers in a replicated setup. 
• The mysqlrplms utility was added, which provides round-robin multi-source replication (a slave server continually cycles through multiple masters in order to store a consolidated data set).

How Can I Download MySQL Utilities?
You can download MySQL Utilities 1.4.2 from the following link using one of the pre-built …

Introduction

MySQL Enterprise Backup (MEB) 3.10 introduces support for encrypted backups by allowing backup images, or single-file backups, to be encrypted. However, backups stored in multiple files in a backup directory can not be encrypted.

Any MEB command that produces a backup image can be optionally requested to encrypt it. The encrypted backup image can be stored in a file or tape in the same way as an unencrypted backup image. Similarly, any MEB command that reads data from a backup image accepts also an encrypted backup image. This means that encrypted backups can be used in all the same situations as unencrypted backup images.

MEB encrypts data with Advanced Encryption Standard (AES) algorithm in CBC mode with 256-bit keys. AES is a symmetric block cipher which means that the same key is used both for encryption and decryption. The AES cipher has been adopted by the U.S. government and it is now used worldwide. …