Tuesday, January 02, 2007

No More MySQL Binary?

If you look in the MySQL download page, then you will see that the latest version displayed is 5.0.27. It's kindda weird, since MySQL development usually never took so much time to release another version which fixed bugs from previous version. But when you look at the MySQL's FTP Site, , you will see that there's an update for MySQL. So, our first guess is that MySQL hasn't update their Download Page, but it's not logical, since MySQL has released 2 updates, 5.0.28 and 5.0.30 (can be seen in the FTP site), so they should have update their download page. As you can see, this applies both to binaries (which is expected with new policies) but also to the source files which were promised to be available.

Why does MySQL hides their binary and source code? Kaj Arnö’s blog mentioned about the new version of MySQL and how it works:
If our changes succeed in their objective, both audiences will benefit from a more stable, feature-rich and high-quality database. The open source benefits for each of the audiences mutually reinforce each other:

* Community users get new features at no-cost to them — funded by paying customers

* Enterprise users get a more stable, reliable and predictably-released product — thanks to community participation

Each of these components of the virtuous circle of open source contributes to the development and spreading of a better MySQL for everyone.

But in reality nowadays, the community never get their result. MySQL didn't publish their FTP site at their download page, and most users that needs to have binary version of newer product will have to build it from the original source code.

Is it time to migrate to PostgreSQL?

References:
MySQL Performance Blog
MySQL Digg
Kaj Arnö’s blog