summaryrefslogtreecommitdiff
path: root/storage
diff options
context:
space:
mode:
authorJon Olav Hauglid <jon.hauglid@oracle.com>2011-03-07 14:30:49 +0100
committerJon Olav Hauglid <jon.hauglid@oracle.com>2011-03-07 14:30:49 +0100
commit5e32755e4cd7d1f8b6c3fd667540f34dacc4c3d2 (patch)
treeead337291e89382883161897b9d38836fc3cf58c /storage
parentbafe24035dbf6d5452d7328ab45d6b43abe52d54 (diff)
downloadmariadb-git-5e32755e4cd7d1f8b6c3fd667540f34dacc4c3d2.tar.gz
Bug #11784056 ENABLE CONCURRENT READS WHILE CREATING
NON-PRIMARY UNIQUE INDEX USING INNODB This patch adds the HA_INPLACE_ADD_UNIQUE_INDEX_NO_WRITE capability flag to InnoDB, indicating that concurrent reads can be allowed while non-primary unique indexes are created. This is an follow-up to Bug #11751388 which enabled concurrent reads when creating non-primary non-unique indexes. Test case added to innodb_mysql_sync.test.
Diffstat (limited to 'storage')
-rw-r--r--storage/innobase/handler/ha_innodb.cc1
1 files changed, 1 insertions, 0 deletions
diff --git a/storage/innobase/handler/ha_innodb.cc b/storage/innobase/handler/ha_innodb.cc
index 3763e6f9cef..bea92903c58 100644
--- a/storage/innobase/handler/ha_innodb.cc
+++ b/storage/innobase/handler/ha_innodb.cc
@@ -2597,6 +2597,7 @@ innobase_alter_table_flags(
| HA_INPLACE_ADD_INDEX_NO_WRITE
| HA_INPLACE_DROP_INDEX_NO_READ_WRITE
| HA_INPLACE_ADD_UNIQUE_INDEX_NO_READ_WRITE
+ | HA_INPLACE_ADD_UNIQUE_INDEX_NO_WRITE
| HA_INPLACE_DROP_UNIQUE_INDEX_NO_READ_WRITE
| HA_INPLACE_ADD_PK_INDEX_NO_READ_WRITE);
}