14 messages in com.mysql.lists.mysqlRe: Upgrading to 5.0.15
FromSent OnAttachments
Robert DiFalco27 Dec 2005 15:32 
Tripp Bishop27 Dec 2005 16:42 
Gleb Paharenko28 Dec 2005 05:03 
Gary Richardson28 Dec 2005 08:09 
Christian Meisinger30 Dec 2005 03:38 
Gary Richardson30 Dec 2005 07:55 
Tripp Bishop03 Jan 2006 15:44 
emie...@micron.com04 Jan 2006 06:24 
Tripp Bishop04 Jan 2006 10:00 
emie...@micron.com04 Jan 2006 11:29 
Tripp Bishop04 Jan 2006 12:01 
Imran Chaudhry05 Jan 2006 05:53 
Kyle05 Jan 2006 18:50 
Gleb Paharenko09 Jan 2006 06:02 
Subject:Re: Upgrading to 5.0.15
From:Gary Richardson (gary@gmail.com)
Date:12/28/2005 08:09:27 AM
List:com.mysql.lists.mysql

We moved directly from 4.0.20 to 5.0.16. Worked like a charm. I had a script that went through and optimized all tables with keys on text/varchar and char fields.

We're also slowly ALTERing innodb tables to get them into the new compact format.

On 12/28/05, Gleb Paharenko <gleb@ensita.net> wrote:

Hello.

Manual recommends to perform an upgrade step by step. So

I suggest you to move to 4.1 at first. When you said 'tablespace'

have you meant that you're using InnoDB tables? I'm not sure about

them, check the change logs to find out any incompatible changes. In

case of MyISAM,very often it is enough just to copy files to the

directory of the new server and repair indexes.

Tripp Bishop wrote:

Howdy all,

I've got a MySQL 4.0.24 database that I'd like to

upgrade to 5.0.15. Is it possible to backup the

tablespace "file" in the mysql data directory and then

install the new database then move the backed up files

into the new installations data directory? Are we

stuck running a mysqldump script? That would take

hours and we'd like to avoid it if at all possible. If

not we'll deal with it but it would be nice to just

move the files.

Thanks,

Tripp

__________________________________

Yahoo! for Good - Make a difference this year.