Re: Assistance with DB (mysql) size optimisation
Simon Buchanan <[email protected]> Wed, 9 Mar 2016 16:10:45 +1300
| Newsgroups | gmane.mail.imap.dbmail |
|---|---|
| Message-ID | <[email protected]> |
Actually your reply here made me re-think. We are using Percona 5.1, so upgrading to 5.5 then 5.6 - so downtime of 5mins. Then using pt-online-schema-change to perform the ALTER the structure without blocking reads or writes. Works a treat! On 8 March 2016 at 10:21:45 PM, Andrea Brancatelli ([email protected]) wrote: As a side node that will require longer time and more space than the ALTER TABLE Engine=InnoDB ROW_FORMAT_COMPRESSED, as you will have to read the table to write the dump, and then read the dump to write the table, opposed to reading the table to write the new one. Furthermore unless you do online gzipping or such the dump will require more space than the new, compressed, table. But, hey, it's your server :-) _______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail