1 |
Alex Efros ha scritto: |
2 |
> Hi! |
3 |
> |
4 |
> I notice you are one of authors for Gentoo's MySQL upgrade guide |
5 |
> http://www.gentoo.org/doc/en/mysql-upgrading.xml |
6 |
> and I've few questions about it. |
7 |
> |
8 |
> # MYSQL --execute="FLUSH TABLES WITH READ LOCK;" |
9 |
> ... |
10 |
> # MYSQL --execute="UNLOCK TABLES;" |
11 |
> |
12 |
> AFAIK MySQL drop any locks when connection closes, so you probably need to |
13 |
> open MySQL client in another console and run FLUSH TABLES/UNLOCK TABLES |
14 |
> there while executing tar in first console between these commands. |
15 |
> |
16 |
> # mysql_upgrade_shell --user=root --password='your_password' \ |
17 |
> --protocol=tcp --datadir="${DATADIR}" |
18 |
> |
19 |
Verified, docs need to be updated, I'm planning to do a bunch of things |
20 |
next three days on mysql this will be one. |
21 |
> In original MySQL upgrade documentation they recommend to run mysql_upgrade |
22 |
> program and there is nothing about mysql_upgrade_shell script. |
23 |
> AFAIK mysql_upgrade_shell is older version of this program (mysql_upgrade |
24 |
> program was added because there no bash to execute mysql_upgrade_shell |
25 |
> script on Win32). |
26 |
> So, what's better to run - mysql_upgrade_shell or mysql_upgrade? Or there |
27 |
> no difference between them now? |
28 |
> |
29 |
mysql_upgrade_shell has survived better to my test but I should redo |
30 |
those now probably mysql_upgrade is better maintained. |
31 |
|
32 |
-- |
33 |
gentoo-server@g.o mailing list |