summaryrefslogtreecommitdiff
path: root/storage
diff options
context:
space:
mode:
authorAnnamalai Gurusami <annamalai.gurusami@oracle.com>2013-03-29 22:11:33 +0530
committerAnnamalai Gurusami <annamalai.gurusami@oracle.com>2013-03-29 22:11:33 +0530
commit036787a919b3cef21cbd5a3fb0afb2f0aed465c8 (patch)
tree5392a91b6960418f381477af9cf6c2ae2fad0bf6 /storage
parent924c2c6f04dea67560c2913b5eaa9d09caeab1a8 (diff)
parent27277df73b5e27cf639b156ee297d24cd469ec45 (diff)
downloadmariadb-git-036787a919b3cef21cbd5a3fb0afb2f0aed465c8.tar.gz
Merge from mysql-5.1 to mysql-5.5
Diffstat (limited to 'storage')
-rw-r--r--storage/innobase/include/dict0mem.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/storage/innobase/include/dict0mem.h b/storage/innobase/include/dict0mem.h
index 5c7d492dbbb..0ee5721d34b 100644
--- a/storage/innobase/include/dict0mem.h
+++ b/storage/innobase/include/dict0mem.h
@@ -127,7 +127,7 @@ This could result in rescursive calls and out of stack error eventually.
DICT_FK_MAX_RECURSIVE_LOAD defines the maximum number of recursive loads,
when exceeded, the child table will not be loaded. It will be loaded when
the foreign constraint check needs to be run. */
-#define DICT_FK_MAX_RECURSIVE_LOAD 30
+#define DICT_FK_MAX_RECURSIVE_LOAD 20
/** Similarly, when tables are chained together with foreign key constraints
with on cascading delete/update clause, delete from parent table could