1 |
On Tue, Feb 16, 2010 at 06:11:13AM +0000, Duncan wrote: |
2 |
> > - If you actually ran mysqld as your own user (Akonadi w/ internal MySQL |
3 |
> > instance), use the mysql_upgrade with suitable parameters to connect |
4 |
> > to the database (as to what those are, you're the one running it, not |
5 |
> > me). |
6 |
> It's automagic from here. I just run kde. What it does, I don't know. I |
7 |
> just don't want it to break! (And upgrade implications will get worse |
8 |
> with kde 4.5 in August, as kmail will be depending on it then, and users |
9 |
> tend to get rather cross when their mail store gets hosed! With 4.4, it's |
10 |
> mainly the address book.) |
11 |
All of that is under the Akonadi side of KDE. I really don't think |
12 |
storing mail inside MySQL is going to be a good idea. |
13 |
|
14 |
> >> Perhaps a note for kde users telling them where their databases are |
15 |
> >> located so they /can/ back them up, etc.) |
16 |
> > I've got no idea where they are located, I just focus on MySQL itself. I |
17 |
> > wasn't even aware of Akonadi's usage until a couple of weeks ago. |
18 |
> What I was suggesting, between the lines, is to coordinate with the kde |
19 |
> project. They may want to create their own upgrade document, which might |
20 |
> be listed in the news release or in a separate one (testing for both mysql |
21 |
> and kde). Hopefully they reply to this thread with whatever their |
22 |
> concerns there might be. |
23 |
I announced it 2 weeks ago, on February 1st, Message-Id: |
24 |
robbat2-20100201T012126-637073772Z@××××××××××××××.net I just hadn't |
25 |
gotten to actually doing it yet due to travel and getting sick on my way |
26 |
home (and Delta doing everything in their power to screw things up, I |
27 |
still haven't got one of my pieces of luggage back yet). |
28 |
|
29 |
As soon as the 72 hours on this news announcement are done, I'm going to |
30 |
be unmasking it. I do expect most of the breakage to come from the |
31 |
client libraries, and NOT any actual data storage issues. If MySQL |
32 |
detects that it's not safe to access a table, it does give you a |
33 |
suitable error to repair the table. |
34 |
|
35 |
mysql_upgrade is actually really just running 'CHECK TABLE ... FOR |
36 |
UPGRADE;' && 'REPAIR TABLE ...' on tables with something that needs to |
37 |
change. Doing a 'REPAIR TABLE ...' globally will cover you if you don't |
38 |
have any other way to issue the check statements manually. |
39 |
|
40 |
That is of course me assuming that you have a way to issue 'REPAIR TABLE |
41 |
...', because that's a critical MySQL command for the DBA/user to know |
42 |
in managing their data. |
43 |
|
44 |
-- |
45 |
Robin Hugh Johnson |
46 |
Gentoo Linux: Developer, Trustee & Infrastructure Lead |
47 |
E-Mail : robbat2@g.o |
48 |
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 |