Our previous GA release of Percona XtraDB Cluster caused a lot of interest and feedback. I am happy to announce next version Percona XtraDB Cluster 5.5.23, which comes with bug fixes and improvements. List of changes: Fixes merged from upstream (Codership-mysql) Support for MyISAM, now changes to MyISAM tables are replicated to other nodes Improvements […]
I am excited to announce the availability of the GA release of our new product Percona XtraDB Cluster. Percona XtraDB Cluster is a High Availability and Scalability solution for MySQL Users and is based on Percona Server 5.5.20. With this release we make clustering very easy and affordable for everyone. You can convert your existing […]
I am happy to announce the availability of beta release of our new product Percona XtraDB Cluster. Percona XtraDB Cluster is High Availability and Scalability solution for MySQL Users and the beta release is based on Percona Server 5.5.20 and the recently released Galera 2.0 GA The main focus in this release: Incremental State Transfer, […]
Percona is glad to announce the release of Percona Server 5.5.19-24.0 on January 13th, 2012 (Downloads are available here and from the Percona Software Repositories). Based on MySQL 5.5.19, including all the bug fixes in it, Percona Server 5.5.19-24.0 is now the current stable release in the 5.5 series. All of Percona ‘s software is […]
Codership team published beta2 of MySQL 5.5.15 with Galera replication https://launchpad.net/codership-mysql and we made port to Percona Server: source code: lp:~percona-dev/percona-server/percona-server-galera-5.5.15 binaries for RedHat/CentOS 6: http://www.percona.com/downloads/TESTING/Galera/Percona-XtraDB-Galera-5.5.15.tar.gz What difference between Percona Server+Galera and MySQL 5.5.15 ? First of course, Percona Server+Galera is based on our XtraDB engine. Second, we provide wsrep_sst_xtrabackup script, which allows to use […]
Codership team announced availability of MySQL/Galera 0.8.1, which is minor release, but actually it has bunch of improvements that makes Galera replication more user friendly (there are many bugs fixed, reported by me personally, what annoyed me a lot). As part of my evaluation activity I ported MySQL/Galera 0.8.1 to Percona Server/Galera 0.8.1 and you […]
A couple of days ago, Dimitri published a blog post, Analyzing Percona’s TPCC-like Workload on MySQL 5.5, which wasÂ a response to my post, MySQL 5.5.8 and Percona Server: being adaptive. I will refer to Dimitri’s article as article . As always, Dimitri has provided aÂ very detailed andÂ thoughtful article, and I strongly recommend reading if […]
Dear Community, The build 17 of MySQL with Percona patches is available. New features in the release: MySQL-5.0.83 is taken as the basis The new patch innodb_use_sys_malloc.patch is added The new patch innodb_split_buf_pool_mutex.patch is added This patch splits the single global InnoDB buffer pool mutex into several mutexes for different purposes. This reduces mutex contention. […]
I am happy to announce next build of our backup tool. This version contains several bugfixes and introduces initial implementation of incremental backup. Incremental backup works in next way. When you do regular backup, at the end of procedure you can see output:
The latest check point (for incremental): '1319:813219999'
>> log scanned up to (1319 813701532)
Transaction log of lsn (1318 3034677302) to (1319 813701532) was copied.
090404 06:03:29 innobackupex: All tables unlocked
090404 06:03:29 innobackupex: Connection to database server closed
innobackupex: Backup created in directory '/mnt/data/tmp'
innobackupex: MySQL binlog position: filename 'db02-bin.001271', position 247627478
090404 06:07:58 innobackupex: innobackup completed OK!
innobackupex: You must use -i (--ignore-zeros) option for extraction of the tar stream.
which gives start point 1319:813219999 for further incremental backup. This point […]
We were doing MySQL Performance evaluation on TPC-H queries for the client and they kindly allowed us to publish results which are very interesting. This is obviously not audited TPC-H run, and it can’t be because we used MyISAM tables which are not ACID complaint. Plus we only measured Power to keep things simple. We […]