diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2018-10-15 14:01:38 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2018-10-15 14:01:38 -0400 |
| commit | ca361554c24e51eed38c8975780fa7dd98d760ed (patch) | |
| tree | 7a4f1b355048a122c95896c26f0141dfb8851fd9 | |
| parent | a05f7053e842d1463c35713ae79e6795b8751dc2 (diff) | |
Check for stack overrun in standard_ProcessUtility().
ProcessUtility can recurse, and indeed can be driven to infinite
recursion, so it ought to have a check_stack_depth() call. This
covers the reported bug (portal trying to execute itself) and a bunch
of other cases that could perhaps arise somewhere.
Per bug #15428 from Malthe Borch. Back-patch to all supported branches.
Discussion: https://postgr.es/m/15428-b3c2915ec470b033@postgresql.org
| -rw-r--r-- | src/backend/tcop/utility.c | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/src/backend/tcop/utility.c b/src/backend/tcop/utility.c index c6d2e26b0ae..03cccad541b 100644 --- a/src/backend/tcop/utility.c +++ b/src/backend/tcop/utility.c @@ -359,6 +359,9 @@ standard_ProcessUtility(Node *parsetree, { bool isTopLevel = (context == PROCESS_UTILITY_TOPLEVEL); + /* This can recurse, so check for excessive recursion */ + check_stack_depth(); + check_xact_readonly(parsetree); if (completionTag) |