diff options
| author | Annamalai Gurusami <annamalai.gurusami@oracle.com> | 2013-03-29 22:01:10 +0530 |
|---|---|---|
| committer | Annamalai Gurusami <annamalai.gurusami@oracle.com> | 2013-03-29 22:01:10 +0530 |
| commit | 27277df73b5e27cf639b156ee297d24cd469ec45 (patch) | |
| tree | 4cdee05b405d77f89ad10c990ad26f303cafc61b /storage/innobase | |
| parent | a6890cce66b05150b4534a5c26918fd3732a51f2 (diff) | |
| download | mariadb-git-27277df73b5e27cf639b156ee297d24cd469ec45.tar.gz | |
Bug #16244691 SERVER GONE AWAY ERROR OCCURS DEPENDING ON THE NUMBER OF
TABLE/KEY RELATIONS
The DICT_FK_MAX_RECURSIVE_LOAD was reduced from 250 to 33 in rb#2058.
But in optimized build, this recursive depth is still too deep and
resulted in stack overflow. So reducing this depth to 20 now.
Diffstat (limited to 'storage/innobase')
| -rw-r--r-- | storage/innobase/include/dict0mem.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/storage/innobase/include/dict0mem.h b/storage/innobase/include/dict0mem.h index 21ae248ce9e..c4948ff7fb2 100644 --- a/storage/innobase/include/dict0mem.h +++ b/storage/innobase/include/dict0mem.h @@ -317,7 +317,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 33 +#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 |