Based on MySQL 5.6.30, including all the bug fixes in it, Percona Server 5.6.30-76.3 is the current GA release in the Percona Server 5.6 series. Percona Server is open-source and free …[Read more]
The problem with Twitter is that we talk about something and before you know it, people forget. (e.g. does WebScaleSQL have an async client library?) How many blog posts are there about Percona Live Santa Clara 2015? This time (2016), I’m going to endeavour to write more than to just tweet – I want to remember this stuff, and search archives (and also note the changes that happen in this ecosystem). And maybe you do too as well. So look forward to more blogs from Percona Live Data Performance Conference 2016. In the meantime, here’s tweets in chronological order from my Twitter search.
- crowd filling up the keynote room for #perconalive
- beginning shortly, we’ll see @peterzaitsev at #perconalive doing his keynote
- #perconalive has over 1,200 attendees – oracle has 20 folk, with 22 folk from facebook …
You would think MySQL storage engines are fairly independent of each other, even in the same environment. Enabling one, or changing its configuration, logically should have no impact on the performance of other engines (such as InnoDB) when they are accessing tables. The reality, however, is more complicated than that!
Now that we’ve shipped TokuDB, we’ve been getting feedback from our community and customers that enabling TokuDB might negatively affect performance – even for queries that don’t touch TokuDB tables (and in some cases, even when TokuDB is kept completely idle).…[Read more]
Based on MySQL 5.7.11, including all the bug fixes in it, Percona Server 5.7.11-4 is the current GA release in the Percona Server 5.7 series. All of Percona’s software is open-source and free, …[Read more]
Based on MySQL 5.6.29, including all the bug fixes in it, Percona Server 5.6.29-76.2 is the current GA release in the Percona Server 5.6 series. Percona Server is open-source and free …[Read more]
After upgrading Percona Server 5.6.28 (and "full stack" of
Percona software) to 5.7.10-3 GA on CentOS 6 and building it from Git Source on Fedora Core 23
yesterday, I've decided to spend some time upgrading Percona
Server on my netbook that plays a role of "home build/test/VMs
server" and runs under Ubuntu 14.04:
openxs@ao756:~$ uname -a
Linux ao756 3.13.0-77-generic #121-Ubuntu SMP Wed Jan 20 10:50:42 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
openxs@ao756:~$ cat /etc/issue
Ubuntu 14.04.4 LTS \n \lIt had the following set of Percona packages (as a result of some tests with Percona XtraDB Cluster I had to use sometime while working there) and mysqld process running after OS …
This post is an update to the status of various MySQL bugs (some with patches) that I’ve filed over the past couple of years (or that people around me have). I’m not looking at POWER specific ones, as there are these too, but each of these bugs here deal with general correctness of the code base.
Firstly, let’s look at some points I’ve raised:
- Incorrect locking for global_query_id (bug #72544)
Raised on May 5th, 2014 on the internals list. As of today, no action (apart from Dimitri verifying the bug back in May 2014). There continues to be locking that perhaps only works by accident around query IDs.Soon, this bug will be two years old.
- Endian code based on CPU type rather than endian define (bug …
Based on MySQL 5.7.10, including all the bug fixes in it, Percona Server 5.7.10-3 is the current GA release in the Percona Server 5.7 series. All of Percona’s software is open-source …[Read more]
Percona is glad to announce the second release candidate of Percona Server 5.7.10-2 on February 8, 2016. Download the latest version from the Percona web site or from the Percona Software Repositories.
Based on MySQL 5.7.10, including all the bug fixes in it, Percona Server 5.7.10-2 is the current Release Candidate release in the Percona Server 5.7 series. All of Percona’s …[Read more]
I planned to continue this series of posts with the one about
MySQL Support engineers who joined us in Oracle while I was
working there, but based on recent events in my life I'd prefer
to postpone it and move directly to the team I worked for during
last 3+ years, Percona Support Team.
Disclamer: In the list below I still try to pay attention to public contribution by each of engineers mentioned to MySQL Community, mostly in a form of bug reports. This is not the only way they contributed, but I have to stick to this format in current series of posts. I also base my comments mostly on my memory and quick search of public sources of information, so I may be mistaking about the roles, time periods and other details. Please, inform me if you think there is something to fix.
So, here is the list of my former colleagues who formed the best MySQL Support team in the industry in 2013-2015 while working with me in …