… have much better performance than MySQL 5.0 – this is due to locking and IO patches from Google integrated in this release… optimization. Should we take Innodb from MySQL 5.4 and merry it with unique Percona patches (adaptive checkpoints, additional undo slots, profiling… lot of customers not quite ready to update to MySQL 5.1 in particular as there is little in this version which…
Post: Call for opinions: Do we need MySQL 5.0 with MySQL 5.4 performance
Post: XtraDB storage engine release 1.0.6-9
… added in Release 8, but somehow it was forgotten) New patch innodb_relax_table_creation Added extended statistics to slow log… Added recovery statistics output when crash recovery (disabled by default) Patch to dump and restore innodb_buffer_pool Fixed bugs: Bug… inconsistent with mysqld Bug #495342: “MySQL 5.1.41 + InnoDB 1.0.6 + XtraDB patches extensions-1.0.6, rev. 127 fails to compile…
Post: XtraDB storage engine release 1.0.3-5
… to MySQL 5.1.34 removed rw_lock patch, so we now use Google’s rw_locks fix crash after upgrade 5.1.31 -> 5.1.33 fix mysql-test Percona XtraDB 1… features requests for new engine and ready to accept community patches. You can monitor Percona’s current tasks and further plans…
Comment: New MySQL Community Release Policies published
… patches (including mine) not some version which my clients will be ready to use 2 years from now. 2) Regarding microsecond patch – 5.1 is not 5.0 (still beta). It is still taking way too… months or so. I had customers having problem with this patch, even though Jeremy tells me they are typically because of…
Post: XtraDB storage engine release 1.0.2-2 (New Year edition)
… release 1.0.2-2 of our XtraDB storage engine. Here is a list of enhancements: split-buffer_pool_mutex The patch… library, to use as drop-in plugin for existing MySQL-5.1.30 installation XtraDB is compatible with existing InnoDB tables (Warning… features requests for new engine and ready to accept community patches. You can monitor Percona’s current tasks and further plans…
Post: XtraDB storage engine release 1.0.2-3 (Spring edition) codename Sapporo
… engine. Here is a list of enhancements: Move to MySQL 5.1.31 Scalability fix — ability to use several rollback segments… have problem with this. New parameters in the XtraDB io patches: innodb_ibuf_max_size — Restrict innodb-insert-buffer size… features requests for new engine and ready to accept community patches. You can monitor Percona’s current tasks and further plans…
Post: XtraDB storage engine release 1.0.3-4 codename Sakura
… to MySQL 5.1.33 Move to InnoDB plugin 1.0.3 more reliable replication, innodb_overwrite_relay_log_info patch now included in… assertions for UNIV_DEBUG new fix for rw_lock patch Percona XtraDB 1.0.3-4 (Sakura) available in source and several… features requests for new engine and ready to accept community patches. You can monitor Percona’s current tasks and further plans…
Post: Percona Server 5.5.14-20.5
… to improve compatibility for those upgrading from MySQL 5.0 or 5.1 prior to version 5.1.24. A fix for a MySQL bug (#27877) introduced an incompatible change in collations in MySQL 5.1… platform-specific distribution: The compilation of the Response Time Distribution patch has been fixed on Solaris (supported platform) and Windows (experimental…
Post: Userstats patches with information schema support
Recently, we added information schema support to Google’s userstats patch. There are three information schema tables added: user_statistics, table… information_schema.user_statistics along with show user_statistics. Links: Patch for 5.0.62 Patch for 5.1.26
Post: Percona builds with patches
…/ deb http://mysqlperformanceblog.com/mysql/debian/5.1/ binary-amd64/ deb http://mysqlperformanceblog.com/mysql/debian/5.1/ source/ Also we have generic RPMs…

