Это первая статья из серии, посвященной сравнению iOS и Android. Вообще говоря, это написано скорее больше для себя, чтобы отметить наиболее интересные моменты и чтобы привести мысли в порядок. Когда пользуешься определённым девайсом со временем привыкаешь к его сильным сторонам, начинаешь их считать обыкновенными, а неудобство от слабых черт доставляет недовольство и сподвигает и искать что-то новое. Так вот, текст для того, чтобы помнить... :)

Основным оппонентом будет Samsung Note 2, т.к. он был у меня непосредственно перед iPhone 5S, и …

MySQL Central is truly a MySQL Community show. This year there are five tracks and the majority of the sessions in all the tracks except Performance and Scalability had many more submissions from the MySQL Community than from Oracle/MySQL. The voting has been tough this year for me. Picking roughly fifty talks out of about two hundred submissions may sound easy. But this year I found only a few topics that were easy to score lowly as they were either off the mark for the conference or not strong enough subjects for the devotion of an hour. So that took it down from two hundred sessions to one ninety seven.

I do not know how the other selectors are making their choices but I had an exhausting time of it. The first pass took me a week part-time to read all the details of each submission without looking at the author in order to judge the talks on their content. Next I look for amazing presenters who have taught me something in the …

While at the keynote of Tomas Ulin at Percona Live MySQL Conference & Expo Santa Clara 2014, he asked the audience what they were running, and most of the audience was on MySQL 5.5 while about 15% of the audience was on MySQL 5.6. This number is steadily increasing I’m sure, so one thing that becomes important is that people will probably start turning on Global Transaction Identifiers (GTIDs). 

As you may already know, MariaDB 10 has a different implementation of Global Transaction ID. To me, this poses a problem in a mixed use environment (or even a migration scenario). Which is why …

There are many MySQL related IRC discussion channels as the ecosystem itself grows. I join the following. Are there any that I’m missing?

Freenode (irc.freenode.net):

• #mysql – main channel for all kinds of end user MySQL related discussions (the noisiest of the lot, naturally)
• #maria – main channel for all kinds of MariaDB related discussions
• #webscalesql – for all kinds of WebScaleSQL discussions
• #percona – main channel for all kinds of Percona related discussions
• #tokutek – main channel for Tokutek discussions (TokuDB or TokuMX)
• SkySQL-specific channels: #maxscale and #mariadb-mgr

OFTC (irc.oftc.net):

• #debian-mysql – for all kinds of Debian MySQL related bits (packaging, bugs, etc.)

Related posts:

1. …

Oracle OpenWorld, taking place Sept 28-Oct 2, 2014 in San Francisco, is the world’s largest gathering of technology and business professionals. The conference includes several dedicated programs focused on specific technologies and solutions, such as Human Capital Management, Customer Experience, and MySQL.

In order to bring more consistency, clarity and visibility to those programs, they have all been renamed "Central". MySQL Connect therefore becomes "MySQL Central @ OpenWorld", and we will use this name moving forward.

MySQL Central @ OpenWorld offers you the opportunity to hear directly from Oracle’s MySQL engineers about the latest MySQL features, enhancements and plans. Best Practices sessions by MySQL customers, community members and partners will help you understand how to make the most of MySQL.

MySQL Central @ OpenWorld includes:

Here on the Percona MySQL Support team, we often see issues where a customer is complaining about replication delays – and many times the problem ends up being tied to MySQL replication slave lag. This of course is nothing new for MySQL users and we’ve had a few posts here on the MySQL Performance Blog on this topic over the years (two particularly popular post in the past were: “Reasons for MySQL Replication Lag” and “Managing Slave Lag with MySQL Replication,” both by Percona CEO Peter Zaitsev).

In …

MySQL, the original brand, the one developed by the MySQL team at Oracle, is steadily evolving. You can feel it if you try every new release that comes out of the milestone release cycle. Or even if you don’t try all of them, just testing a release once in a while gives you something to think about.

The engineers at Oracle are trying hard to improve the defaults. If you are the out-of-the-box type, and just install the new version on top of the previous one, leaving the same setup in place, you may be up for a for a few surprises. It’s the marketing, see? They tell you that just by replacing your old MySQL (5.1 or 5.5) with MySQL 5.6 you get 30% to 70% performance improvement. Which happens to be true, not only because the server is better, but also because they have changed the defaults. However, this change in defaults may come with some serious consequences for the ones who …

There are uprades for our Galera Cluster in the repository:

> yum info galera
Installed Packages
Name        : galera
Arch        : x86_64
Version     : 25.3.2
Release     : 1.rhel6
Size        : 29 M
Repo        : installed
From repo   : mariadb

Available Packages
Name        : galera
Arch        : x86_64
Version     : 25.3.5
Release     : 1.rhel6
Size        : 7.6 M
Repo        : mariadb

> yum info MariaDB-Galera-server
Installed Packages
Name        : MariaDB-Galera-server
Arch        : x86_64
Version     : 5.5.36
Release     : 1.el6
Size        : 102 M
Repo        : installed
From repo   : mariadb

Available Packages
Name        : MariaDB-Galera-server
Arch        : x86_64
Version     : 5.5.37
Release     : 1.el6
Size        : 25 M
Repo        : mariadb

Rolling Upgrade

Let’s do a Rolling Upgrade. This nice feature of Galera allows us to upgrade to the new version without taking the cluster offline.

This is …

Don't miss your opportunity to learn about Continuent Tungsten via our free "Setup & Operate" webcast series. These free webcasts include live presentations and interactive Q&A.Webcast OverviewsSetup & Operate Tungsten ReplicatorMay 15th, 10:00 am PDTTungsten Replicator is an innovative and reliable tool that can solve your most complex replication problems. We will introduce Replicator

Before upgrading from MySQL 5.5 to 5.6, I read the relevant page in the reference manual and found this section about the storage format change for DATETIME, TIME, TIMESTAMP data types to support microseconds:

Incompatible change: For TIME, DATETIME, and TIMESTAMP columns, the storage required for tables created before MySQL 5.6.4 differs from storage required for tables created in 5.6.4 and later. This is due to a change in 5.6.4 that permits these temporal types to have a fractional part. After upgrading from MySQL 5.5 to MySQL 5.6.4 or later, it is recommended that you also upgrade from MySQL 5.5 to MySQL 5.6 TIME, DATETIME, and TIMESTAMP types...

The problem is that the manual doesn't …