6 messages in com.mysql.lists.clusterupgraded from 5.0 to 5.1 but database...
FromSent OnAttachments
Paul Maunders11 Sep 2006 06:41 
Anatoly Pidruchny11 Sep 2006 06:53 
Paul Maunders11 Sep 2006 07:20 
Mikael Ronström11 Sep 2006 07:24 
Anatoly Pidruchny11 Sep 2006 08:00 
Paul Maunders11 Sep 2006 08:20 
Subject:upgraded from 5.0 to 5.1 but database size the same
From:Paul Maunders (pa@fubra.com)
Date:09/11/2006 06:41:30 AM
List:com.mysql.lists.cluster

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Hi,

I have just upgraded our deployment of MySQL cluster from 5.0 to 5.1 - I did a backup, deleted 5.0, installed 5.1 and then ran ndb_restore to get all the data back.

A lot of the space in the various tables was previously taken up by VARCHARS so I expected the 5.1 version of the database to be significantly smaller, however after restoring the data, it seems that the overall database size has remained the same.

Is this because I restored a backup of a 5.0 database and it somehow maintained the varchar "padding"?

Does anyone know of anyway that I can get MySQL to rebuild the tables so that VARCHARS are stored correctly?

Regards,

- --

Paul Maunders Fubra Limited -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFBWehsYtjtAM5Dp4RAiRRAJ48h3n9+pO+VC1aFR9PWSUp8LZCsQCfYpHS HaIxD04LcGe8Tdzy+S89Pao= =qjOu -----END PGP SIGNATURE-----