I am upgrading minor MySQL versions, 5.0.67 to 5.0.84
I have a master-master replication setup, and want to upgrade both installations.
The ideal procedure for upgrading mysql using the mysql_upgrade command is to have binary logging turned off during the execution of mysql_upgrade.
My situation is I do not want to turn off binary logging for the entire server, I would like to turn off binary logging just for the session of the mysql_upgrade connection.
mysql_upgrade does not support anything like --disable-log-bin (which seems is a feature that should be supported for this cli app)
So it seems my only option is to turn off binary logging for the entire server while I execute mysql_upgrade. Which also means blocking write access to the server while it runs so that statements I do want logged for replication do not occur while binary logging is off.
Is there another simple way to achieve this? Or what is best practice that achieves the least amount of down time?
Alternately, there are sql files in the share directory of each archive:
mysql-5.0.67-linux-i686-glibc23/share/
|-- fill_help_tables.sql
|-- mysql_fix_privilege_tables.sql
|-- mysql_system_tables.sql
|-- mysql_system_tables_data.sql
|-- mysql_system_tables_fix.sql
`-- mysql_test_data_timezone.sql
mysql-5.0.84-linux-i686-glibc23/share/
|-- fill_help_tables.sql
|-- mysql_fix_privilege_tables.sql
|-- mysql_system_tables.sql
|-- mysql_system_tables_data.sql
|-- mysql_system_tables_fix.sql
`-- mysql_test_data_timezone.sql
Is it true (yes or no) that the difference between these 6 sql files from one distribution to the next is what would be changed if the mysql_upgrade was executed to upgrade an installation from 5.0.67 to 5.0.84 ?
This is a repost from the install forum, as my question had not been answered yet.
http://forums.mysql.com/read.php?11,274796,274796#msg-274796