4 ms·
Its one of the big reasons I am looking at switching. I have been dumping the table and reloading it in using a new name and the renaming the tables to get arou
by boyter 14y ago
Its one of the big reasons I am looking at switching. I have been dumping the table and reloading it in using a new name and the renaming the tables to get around this issue but its hardly ideal.
- AaronBBrown 14y agopt-online-schema-change should resolve that issue for you: http://www.percona.com/doc/percona-toolkit/2.1/pt-online-schema-change.html http://www.percona.com/doc/percona-toolkit/2.1/pt-online-sch...
- boyter 14y agoSeems the risks are such my approch works just as well, "pt-online-schema-change modifies data and structures. You should be careful with it, and test it before using it in production. You should also ensure that you have recoverable backups before using this tool." With that being the case what im doing is fine I guess.
- AaronBBrown 14y agoBecause there is a disclaimer, you are disregarding a thoroughly tested product that solves your exact problem? One which is released by one of the premier MySQL consultancies with the author of "the" MySQL book as the designer?
- boyter 14y agoI don't pay for support. So yes.
- AaronBBrown 14y agoYou could make the same exact disclaimer about SQL statement and it would be true: "INSERT modifies data and structures. You should be careful with it, and test it before using it in production. You should also ensure that you have recoverable backups before using this tool." "ALTER modifies data and structures. You should be careful with it, and test it before using it in production. You should also ensure that you have recoverable backups before using this tool." It's just good advice to test stuff before you use it in production. Discarding an awesome product simply because the authors (responsibly) mention that you should probably test it out seems overly paranoid and would severely limit your choices. Percona Toolkit is the most well known and reliable set of tools out there in the MySQL ecosystem.
- GrumpySimon 14y agoWhat are you doing that you need to alter your schema so often?!
- boyter 14y agoIts not that I do it often, its how long it takes. An alter on a 60 gig table takes hours, during which your table is locked which is totally unacceptable.
- einhverfr 14y agoWhat's funny is I used to use MySQL for db prototyping because altering schemas on PostgreSQL was such a pain (prior to 7.3). Now it is much better.