From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Mon, 15 Oct 2018 18:01:38 +0000 (-0400)
Subject: Check for stack overrun in standard_ProcessUtility().
X-Git-Tag: REL9_6_11~32
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=ca361554c24e51eed38c8975780fa7dd98d760ed;p=postgresql

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
---

diff --git a/src/backend/tcop/utility.c b/src/backend/tcop/utility.c
index c6d2e26b0a..03cccad541 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)