Re: Assistance with DB (mysql) size optimisation
Reindl Harald <[email protected]> Thu, 3 Mar 2016 22:12:54 +0100
| Newsgroups | gmane.mail.imap.dbmail |
|---|---|
| Organization | the lounge interactive design |
| Message-ID | <[email protected]> |
Am 03.03.2016 um 22:08 schrieb Simon Buchanan: > > On 3 March 2016 at 11:36:59 PM, Andrea Brancatelli > ([email protected] <mailto:[email protected]>) wrote: >> >> Yes you can proceed easily with those two settings and have a first >> bigger improvement. >> >> If you're switching away from dbmail I wouldn't go trough the hassle >> of upgrading, since the upgrade need to reparse all the message to use >> the de-deduplication features. >> >> Note: the ALTER TABLE will perform the OPTIMIZE TABLE, so you don't >> need to run the two commands, just go for the ALTER TABLE. >> > Thanks for the reply - my thoughts with the upgrade. The issue > with OPTIMISE TABLE is that it needs the same amount of space to do the > optimise, plus the tables are write locked whist this happens (is this > correct?) on a modern setup (MariaDB 10.0.x) they are not locked in your case - yes, they are _______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
signature.asc
(application/pgp-signature, 181 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlbYqNcACgkQhmBjz394AnlKsACeIkkn5WiLM2YBx3tqyAeHSlxy aGoAnAvFnM30gA5aBOMXcQK1C/1ukluf =govv -----END PGP SIGNATURE-----