Depending on the "seriousness" of your environment you can read the changelogs and upgrade if you don't see any showstoppers. I have hardly ever seen any problems with minor version upgrades of mysql. Of course what Rob says is true, and it is a good idea to test things out in a test environment first. But I know many environment where it is "okay" to just run the upgrade, as long as it is a minor version upgrade. I guess it depends on the type of production environment you are running in.
be careful though! Walter On Mon, Apr 5, 2010 at 11:17, Rob Wultsch <wult...@gmail.com> wrote: > On Tue, Mar 30, 2010 at 6:36 AM, Marco Baiguera > <marco.baigu...@gmail.com> wrote: >> Hello everyone, >> i am quite new to mysql and i recently begin to work with a company >> who is using mysql 5.0.45 in production. >> i think this version is too old and would like to upgrade to the most >> recent 5.0.xx >> >> my os is CentOS release 5.3. >> >> is it safe to simply use "yum upgrade mysql" ? >> >> are there any important differences i should be aware of between >> 5.0.45 and 5.0.77 ? >> any diffferences in password encoding etc. ? >> >> the db is properly backed up and replicated on two 5.0.77 slaves. >> >> thank you >> Marco >> > I would not simply upgrade. I would upgrade the test environment first > and have the development team sign off that there were no bad effects > caused by the upgrade. > > The first version of 5.0 that I think is particularly useable and not > buggy is 5.0.67. I suggest that this is worth the upgrade. > > In theory there are not significant differences between 5.0 versions > after GA other that bug fixes. I *do not* trust this. > > > > -- > Rob Wultsch > wult...@gmail.com > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/mysql?unsub=li...@olindata.com > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
