![]() ![]() Mysql> # Modify the index can be instant if it's a trivial change Mysql> CREATE TABLE t1 (a INT, b INT, KEY(b)) If it can not be done, then server will try INPLACE algorithm and if that can not be supported by SE, server will finally try COPY algorithm. Furthermore, if ALGORITHM is not specified at all, server will first try the DEFAULT=INSTANT algorithm. This can now be achieved by (always) specifying ALGORITHM=INSTANT, this will guarantee that either the operation is done instantly or not at all. Many users have asked us about a way to avoid time consuming schema changes. The DDL is externalized after it completes. If replication was involved, user may have to wait a even longer time for slave to be ready.This steals resources from user transactions. The DDL operation is resource hungry and puts a high demand on CPU, Memory and IO. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |