Percona-release-noarch Percona-Release YUM repository - noarch 26 Mysql56-community MySQL 5.6 Community Server 112 Mysql-tools-community MySQL Tools Community 18 Mysql-connectors-community MySQL Connectors Community 12 For example using Oracle ~]# yum repolist APT theoretically is also able to install older versions, but command “apt-cache madison …” returns only the latest one for me. In this article I will focus on YUM as it seems this is the only one currently offering multiple versions from official repositories of Oracle and Percona MySQL variants. My idea was to remind about this last method as maybe the least known one. * point to a particular version just using default package-management utility. * have database instance images with all software prepared, * have custom local repository mirror where you decide when and which version gets there, and just update from there using yum/apt, * download specific version packages manually and then install them, Quite often DBAs want the same MySQL version to be installed on all database instances, regardless of what actually is the latest version available in the software provider’s repository. However there is also a risk of some regression or a new bug introduction as a side effect of code changes. In theory each new version is supposed to be better as usually it contains a handful of bug fixes and even new or improved functionality. There may be several reasons for that, where I think the most common is when a new version should spend some time in testing or a staging environment before getting to production. Sometimes it is desired to use particular software versions in production, and not necessary the latest ones.
0 kommentar(er)
