I love the answer
On Fri, Nov 18, 2011 at 10:59 PM, Daevid Vincent dae...@daevid.com wrote:
Ever heard the old saying, If it ain't broke, don't fix it. ;-)
I'd say that as a general rule:
1. if you aren't experiencing problems then don't upgrade.
2. if you aren't subject to any vulnerabilities that may be found, then
don't upgrade
3. if you don't need a new feature introduced, then don't upgrade
4. if you need to be up 100%, then don't upgrade
Having said that, it is possible to upgrade with minimal downtime if you're
smart about it.
Get another server (or two or three) that is a clone of the existing ones.
Upgrade those. Test those. Swap over.
Then for the next release, do the same thing with the servers you now have
as the spares.
If you're in such a mission critical situation, you should have spare
servers and live hot-swapable backups anyways right.
-Original Message-
From: Neil Tompkins [mailto:neil.tompk...@googlemail.com]
Sent: Friday, November 18, 2011 11:54 AM
To: MySQL ML
Subject: How often should we upgrade MySQL version
We are running MySQL 5.1.46 with master to master replication with 3 other
servers for 3 different websites in 3 different parts of the world.
My question is how often should we be looking to upgrade our MySQL version
considering we can't really afford any downtime.
Thanks
Neil
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=dae...@daevid.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
http://lists.mysql.com/mysql?unsub=muadshib...@gmail.com
--
*___*
*
*
السجل .. كل الأخبار من كل مكان
www.alsjl.com
صفحة السجل على فيسبوك
http://www.facebook.com/alsjl
*Muad Shibani*
*
*
Aden Yemen
Mobile: 00967 733045678
www.muadshibani.com