The MySQL 5.1 GA Release will be on or about Dec. 6th, 2008.

How do I know?
(more…)

We made new binaries for MySQL 5.0.67 build 7 which include patches we recently announced.

The -percona release includes:

PLAIN TEXT CODE:

1. | innodb_check_defrag.patch                        | Session status to check fragmentation of the last InnoDB scan                            | 1.0     | Percona <info@percona.com>       | GPL     | The names are Innodb_scan_*                      …

There are a few small changes in MySQL 5.1.29.
SHOW PROFILESIt was already in a preview, but now SHOW PROFILES is available in 5.1 binaries. As you may recall, it is not active …

Google patches V1 contain interesting patch to mirror binary log on slave. Although Google is preparing GlobalTransactionId patch, which going to be replacement for MirroredBinlogs, we still think mirroring binary logs is very useful for:

• Backup of binary logs in real time
• High availability, to switch master load to slave with mirrored binary logs

By request of our friends EngineYard we extracted this patch from Google's patchset and going to include in our next releases. Actually our patch contains features for both MirroredBinlogs and FastMasterPromotion patches, as second provides feature to make slave as master in case of main master failure.

At …

We made new patches, improved previous and want to announce new builds for 5.0.62, 5.0.67 and 5.1.26 versions. One of biggest changes we separated releases of 5.0 into two branches.
First, just "-percona" release is more stable and contains only stable and proven on many installation patches. Second is "-percona-highperf" release, which contains experimental patches that can improve performance significantly. On this stage "percona-highperf" contains patches from Yasufumi Kinoshita (more info on Maximum performance of OLTP benchmark is not so scalable on multi-cpu.
Most important patch "split_buf_pool_mutex" to separate InnoDB buffer->pool mutex into several, and it allows to get 1.5x - 2.5x improvements in DBT2 benchmarks on 8cores boxes (benchmark results is coming and will be published)

For all three versions we added SHOW PATCHES command, which is based …

In two words: online operations. In a paragraph: Forget partitioning, row-based replication and events. The big reasons most people are going to salivate over 5.1, and probably start plans to upgrade now, are the online operations:

• online ALTER TABLE for column rename, column default value change, and adding values to the end of an ENUM/SET
• Online, table-based logging. No more need to restart your server to enable or change the general or slow query logs. You can have the standard file-based output or choose a table format…which you can query.

(more…)

Today I’ve managed to finish initial version of our bounces-handler package we use for mailing-related stuff in Scribd.

Bounces-handler package is a simple set of scripts to automatically process email bounces and ISP‘s feedback loops emails, maintain your mailing blacklists and a Rails plugin to use those blacklists in your RoR applications.

This piece of software has been developed as a part of more global work on mailing quality improvement in Scribd.com, but it was one of the most critical steps after setting up reverse DNS records, DKIM and SPF.

The package itself consists of two parts:

• Perl scripts to process incoming email:
  • bounces processor — could be …

The MySQL Community version is different in theory from the Enterprise version in relation to the following points:

0) It’s free
1) It has community patches
2) It is released less often
3) It is tested less strictly

In reality, the first two differences are not applicable — the binaries and source code for Enterprise can be freely and legally downloaded at http://mirror.provenscaling.com/mysql/enterprise/. The process for adding community patches to the MySQL source code has not been changed sufficiently to be able to actually add community patches and encourage more community development.

I understand that MySQL (and now Sun) needs to make money. I also understand that development takes a lot of effort, and seeing an ROI is important. The Community/Enterprise split was designed to have tradeoffs on both sides. …

In http://www.mysqlperformanceblog.com/2008/07/01/should-we-proclaim-mysql-community-edition-dead/, Peter Zaitsev wonders if MySQL’s community edition is dead.

The title of Peter’s inquiry is somewhat misleading, as the database itself works fine. He clarifies a bit with, “there suppose to be 2 yearly binary releases (which are overdue) and 4 predictable yearly source releases, which we have not seen either.” I thought it was clear that “2 per year” doesn’t mean “one every six months”. It’s been eight months, sure. And I don’t actually believe that MySQL is going to have one source release per month until November, to make up for the lack of source releases. However, it’s certainly possible, if not probable.

The fact remains, however, that if you’re just looking for stable, recent, …

Big changes in this release.

Features:

• Talkback report for local script backups to report back to monolith console
• Status page now summarizes all Codes and failed server connections for past 24 hours
• Install now has correct data import for user setup and system settings
• More GRAPHS!
• Improved logic for analytics and automated tuning recommendations, fixed thread_status bug
• Change request document generation
• Full HTML reporting for statistics gathering and tuning report
• XML API page for custom export of data with all fields available for output
• Integrates with VisualMining: see api-monitor-visualmining.php file
• Data table for index+data size reporting of all monitored databases
• Improved table information gathering via INFORMATION_SCHEMA - no more SHOW commands …