I really like the article.

I had to use lock_get_mode_str() instead of lock_get_mode(). And the bitmap was printed differently.

(gdb) p $rowlock
$3 = (ib_lock_t *) 0x7f9f94011d40
(gdb) p lock_get_mode($rowlock)
No symbol "lock_get_mode" in current context.
(gdb) p lock_get_mode_str($rowlock)
$4 = 0xc346b8 "X"

(gdb) x /4t $rowlock + 1
0x7f9f94011d88: 00000000000000000000000000011110 00000000000000000000000000000000 00000000000000000000000000000000 00000000000000000000000000000000

This is with 5.6.10 on Linux (64-bit).

And maybe it's better to put the PDF link in at the beginning of the article.

Since Tarantool stored procedure API was extended with socket I/O, a whole universe of applications for data-enriched networking (routing, proxying, PUSH-notifications, and so on) has become possible.

But there is one case which doesn't lend itself so easily: anything MySQL. The first scenario I'd love to support is when Tarantool works as a smart write-back cache for MySQL, providing a higher update RPS, but automatically maintaining a slightly dated copy of all the data in a relational database.

One dramatic shortcoming of MySQL universe, which, IMHO, if addressed properly, could spark a whole new set of uses and third-party solutions, is the clumsiness of the client-server protocol.

The MySQL client-server protocol is unnecessarily hard to implement: it is built on top of a layered design, with built-in compression and transport-level tricks to be able to communicate over unreliable protocol such as …

Since Tarantool stored procedure API was extended with socket I/O, a whole universe of applications for data-enriched networking (routing, proxying, PUSH-notifications, and so on) has become possible.

But there is one case which doesn't lend itself so easily: anything MySQL. The first scenario I'd love to support is when Tarantool works as a smart write-back cache for MySQL, providing a higher update RPS, but automatically maintaining a slightly dated copy of all the data in a relational database.

One dramatic shortcoming of MySQL universe, which, IMHO, if addressed properly, could spark a whole new set of uses and third-party solutions, is the clumsiness of the client-server protocol.

The MySQL client-server protocol is unnecessarily hard to implement: it is built on top of a layered design, with built-in compression and transport-level tricks to be able to communicate over unreliable protocol such as …

The Texas Linuxfest might be the ‘little brother’ of the SCaLE show. While a smaller shower in length, it fells much more muscular. I had a full room for a session on The Proper Care and Feeding of a MySQL Database. The audience was sharp, asked amazingly great questions, and hungry for MySQL 5.6 features. And at the booth I was pleasantly inundated with MySQL questions and proud DBAs bragging about their instances.

If you missed the this show this year, please make the trip to Austin next year. You’ll not be disappointed.

This week we discuss MySQL Views. Ear Candy is GRANTs and replication and At the Movies is a presentation by Giuseppe Maxia talking about "Creating Multi-Master clusters with Tungsten Replicator".

Events
DB Hangops - every other Wednesay at noon Pacific time

Upcoming MySQL events

Training
SkySQL Trainings

Tungsten University trainings

read more

Lately more people ask me for comparisons between Percona Server & MariaDB. There isn’t a definitive blow-by-blow feature comparison yet, but it’ll come soon.

All that said, its great to see new features from MariaDB make it into Percona Server. The features that I’ve managed to track: group commit for the binary log, threadpool and atomic write support for Fusion-io devices.

It started with the group commit for the binary log feature in Percona Server 5.5.18-23.0 ( …

I just got back from a vacation to see articles about Business Source Licensing. I’ve divided my thoughts into four parts here: Opensource and its merits, Is unpaid opensource usage bad?, MariaDB’s “Problem”, Business Source Licensing. If you haven’t read them yet, here’s some mandatory reading:

1. Open source: Its true cost and where it’s going awry by Monty Widenius
2. …

Would you like to work with the biggest websites and social networks in the world? Do you want to support large enterprises with their database initiatives? Would you like to assist ISVs and OEMs providing the technology that powers their products?

In the MySQL Sales Consulting organization we do just that. Oracle is hiring for MySQL Sales Consultants in multiple locations, including the US, Canada, and Romania, to support MySQL partners, customers and prospects, evangelize our products, assist marketing and cooperate with product management to shape the future of MySQL. Sound interesting? Click the following links for additional details on these openings:

• …

MySQL Connector/Net 6.7.3, a new version of the all-managed .NET driver for MySQL has been released.  This is the second beta release intended to introduce users to the new features in the release. This release is feature complete, it should be stable enough for users to understand the new features and how we expect them to work. As is the case with all non-GA releases, it should not be used in any production environment. It is appropriate for use with MySQL server versions 5.0-5.7.

After upgrading to Percona’s patched MySQL 5.1*, end users were having connectivity problems, and reporting errors such as:

OperationalError: (2003, "Can't connect to MySQL server on 'db-amo-ro' (110)")

TimeoutError: Request timed out after 5.000000 seconds

OperationalError: (1135, "Can't create a new thread (errno 11); if you are not out of available memory, you can consult the manual for a possible OS-dependent bug")

We had these same problems a while back, before increasing ulimit settings in /etc/sysconfig/mysqld. Oracle’s MySQL startup script specifically sources this file:

[ -e /etc/sysconfig/$prog ] && . /etc/sysconfig/$prog

However, we saw these errors again when we upgraded to Percona’s MySQL 5.1. At first we thought that it was because Oracle’s startup script is /etc/init.d/mysqld and Percona’s …