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 when I
upgraded from 5.0 to 5.1. I recall they were mostly procedure/trigger
related. I don't think I ever had any problems with minor
updates with the 5.0 series though.
I just updated to 5.1.47 from .45 and now mysqldump is segfaulting,
mysql_upgrade ran fine but it didn't help:
mysqldump --quick --lock-all-tables --force --routines --triggers \
--all-databases --add-drop-table --add-drop-database -u $user -p$pass > \
${dir}/all_databases.sql
mysqldump: Couldn't execute '': (1064)
Segmentation fault (core dumped)
#0 0x0124088c in mysql_fetch_row () from
/usr/local/lib/mysql/libmysqlclient.so.20.0
--
Antti Harri
