Today I recommended MySQL 5.1
Today I recommended that a customer begin using MySQL 5.1 for development of their new product. There is virtually no risk of doing this, and in fact, the risk of not doing so is quite material. Upgrading the database later would be silly when you could start using it now and find out how best to work with it. Notice that the single criterion I’m mentioning is risk, not features.
I just wanted to mention this in case it appears that I’m anti-5.1. I’m not. I’m all for it when it’s appropriate.
For their existing product, which will end-of-life when the new one is done, I suggested that they just upgrade to the latest stable Percona build. They’re on 5.0.37, and a lot of bugs have been fixed since then. And they need to measure what the application is doing, and the Percona builds give significantly more insight into that.
Further Reading:
That’s in line with Open Query’s general approach “pick the latest for development, you’ll know all about its quirks when you’re done so then you know it’s safe” (shortcuts taken here for brevity)
Arjen Lentz
20 Dec 08 at 6:26 am
I think this is a safe approach for a brand new product, since by the time it gets to the phase where is relies on stability, the major bugs will have been fixed
Shlomi Noach
20 Dec 08 at 9:35 am
Couldn’t you just setup MySQL 5.1 as slave and test your current application against it? That can give you 95% coverage.
Ernesto Vargas
21 Dec 08 at 9:21 pm
[...] ç¾åœ¨è©²æ˜¯ MySQL 5.1 上線的時候了，High Performance MySQL 的主è¦ä½œè€…如æ¤å»ºè°ã€‚ [...]
Ant » Blog Archive » Time to Upgrade to MySQL 5.1 & New XtraDB
22 Dec 08 at 12:08 pm
High Performance, respect
Разработка Ñайтов
28 Dec 08 at 5:07 pm
[...] Today I recommended MySQL 5.1 [...]
Install MySQL
29 Dec 08 at 10:59 pm