Hi,
On Mon, 31 May 2010, Uwe Dippel wrote:
2. I wasn't aware of the need to run mysql_upgrade after an(y) upgrade.
Actually, the man page says it should be done after any upgrade.
Should this eventually be mentioned in the install message?
I wasn't aware either and I had some weird problems
On Tue, Jun 1, 2010 at 5:18 PM, Antti Harri i...@openbsd.fi wrote:
I wasn't aware either and I had some weird problems when I upgraded from 5.0
to 5.1. I recall they were mostly procedure/trigger related.
Yep, that's what the mysql_upgrade corrected here, mostly.
Still, maybe someone should
On Tue, 1 Jun 2010, Antti Harri wrote:
I just updated to 5.1.47 from .45 and now mysqldump is segfaulting,
mysql_upgrade ran fine but it didn't help:
I would like to warn other users, that update totally broke mysql
here, I'm getting this also:
General error: 1548 Cannot load from mysql..
On 1/06/2010 11:35 PM, Antti Harri wrote:
On Tue, 1 Jun 2010, Antti Harri wrote:
I just updated to 5.1.47 from .45 and now mysqldump is segfaulting,
mysql_upgrade ran fine but it didn't help:
I would like to warn other users, that update totally broke mysql
here, I'm getting this also:
(I hope I'm the only one who fell for this.)
If you happen to have
skip-bdb
in your my.cnf, do not update to 4.7 (or the like).
My MySQL failed miserably at start:
100531 20:37:22 mysqld_safe Starting mysqld daemon with databases from
/var/mysql
100531 20:37:23 [Note] Plugin 'FEDERATED' is
