mysql-community 5.6.26-2.el5 install changes default config variable
Posted by:
7 reeds
Date: July 31, 2015 10:42PM
Hi,
I did a yum upgrade yesterday (July 30, 2015) of MySQL-Community server from the MySQL repo. This was applied on three identical platforms. Two of the platforms behave normally but one gave use major issues for a while.
The "broken" install somehow turned the MySQL variable "explicit_defaults_for_timestamp" to ON while the other two machines stayed with the default (I think) value of OFF.
This was eventually tracked down and the variable is now in the one machine's config file and is set to OFF.
My question is: is this sort of config flip-flop on install "normal"? I've used MySQL for over a decade and this is the first case of this I have run across.
mysql.x86_64 5.6.26-2.el5 installed
mysql-community-client.x86_64 5.6.26-2.el5 installed
mysql-community-common.x86_64 5.6.26-2.el5 installed
mysql-community-devel.i386 5.6.26-2.el5 installed
mysql-community-devel.x86_64 5.6.26-2.el5 installed
mysql-community-libs.i386 5.6.26-2.el5 installed
mysql-community-libs.x86_64 5.6.26-2.el5 installed
mysql-community-libs-compat.x86_64 5.6.26-2.el5 installed
mysql-community-release.noarch el5-5 installed
mysql-community-server.x86_64 5.6.26-2.el5 installed
Subject
Written By
Posted
mysql-community 5.6.26-2.el5 install changes default config variable
July 31, 2015 10:42PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.