public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-user] mysql upgrade 5.5 > 5.6 mysql_upgrade needed?
@ 2015-03-31 20:27 Marko Weber | 8000
  2015-03-31 21:44 ` Neil Bothwick
  2015-04-01  7:14 ` hydra
  0 siblings, 2 replies; 3+ messages in thread
From: Marko Weber | 8000 @ 2015-03-31 20:27 UTC (permalink / raw
  To: Gentoo User


hello list,
again i have to ask.
Do i need to run mysql_upgrade after upgrading mysql 5.5 > 5.6 ?
I ask because the post install text recommend this after an major 
upgrade.
On the Mysql Website is a major upgrade 5.5 > 6.0, not 5.5 > 5.6
So i ask you guys.
Any can help me?

thank you

marko




^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [gentoo-user] mysql upgrade 5.5 > 5.6 mysql_upgrade needed?
  2015-03-31 20:27 [gentoo-user] mysql upgrade 5.5 > 5.6 mysql_upgrade needed? Marko Weber | 8000
@ 2015-03-31 21:44 ` Neil Bothwick
  2015-04-01  7:14 ` hydra
  1 sibling, 0 replies; 3+ messages in thread
From: Neil Bothwick @ 2015-03-31 21:44 UTC (permalink / raw
  To: gentoo-user

[-- Attachment #1: Type: text/plain, Size: 463 bytes --]

On Tue, 31 Mar 2015 22:27:38 +0200, Marko Weber | 8000 wrote:

> Do i need to run mysql_upgrade after upgrading mysql 5.5 > 5.6 ?
> I ask because the post install text recommend this after an major 
> upgrade.

Do you *need* to? Possibly not. Should you do it? Yes.

If you run it unnecessarily, it simply tells you so, so there is no harm
in running it after every upgrade.


-- 
Neil Bothwick

Please rotate your phone 90 degrees and try again.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [gentoo-user] mysql upgrade 5.5 > 5.6 mysql_upgrade needed?
  2015-03-31 20:27 [gentoo-user] mysql upgrade 5.5 > 5.6 mysql_upgrade needed? Marko Weber | 8000
  2015-03-31 21:44 ` Neil Bothwick
@ 2015-04-01  7:14 ` hydra
  1 sibling, 0 replies; 3+ messages in thread
From: hydra @ 2015-04-01  7:14 UTC (permalink / raw
  To: gentoo-user

[-- Attachment #1: Type: text/plain, Size: 1402 bytes --]

On Tue, Mar 31, 2015 at 10:27 PM, Marko Weber | 8000 <weber@zbfmail.de>
wrote:

>
> hello list,
> again i have to ask.
> Do i need to run mysql_upgrade after upgrading mysql 5.5 > 5.6 ?
> I ask because the post install text recommend this after an major upgrade.
> On the Mysql Website is a major upgrade 5.5 > 6.0, not 5.5 > 5.6
> So i ask you guys.
> Any can help me?
>
> thank you
>
> marko
>
>
>
Yes, you need to - it IS a major upgrade.

Check out http://dev.mysql.com/doc/refman/5.6/en/mysql-nutshell.html and
http://dev.mysql.com/doc/refman/5.6/en/upgrading-from-previous-series.html

It states:
"To upgrade to 5.6 from any previous version, MySQL recommends that you
dump your tables with *mysqldump*
<http://dev.mysql.com/doc/refman/5.6/en/mysqldump.html> before upgrading
and reload the dump file after upgrading. Use the --all-databases
<http://dev.mysql.com/doc/refman/5.6/en/mysqldump.html#option_mysqldump_all-databases>
option to include all databases in the dump. If your databases include
stored programs, use the --routines
<http://dev.mysql.com/doc/refman/5.6/en/mysqldump.html#option_mysqldump_routines>
and --events
<http://dev.mysql.com/doc/refman/5.6/en/mysqldump.html#option_mysqldump_events>
options as well."

So either you dump/restore (safest but harder with downtime - except when
you run replication and switch masters) or you do upgrade on the fly and
run mysql_upgrade.

[-- Attachment #2: Type: text/html, Size: 2406 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2015-04-01  7:14 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-03-31 20:27 [gentoo-user] mysql upgrade 5.5 > 5.6 mysql_upgrade needed? Marko Weber | 8000
2015-03-31 21:44 ` Neil Bothwick
2015-04-01  7:14 ` hydra

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox