From: Pavan Deolasee <pavan.deolasee@gmail.com>
Date: Mon, 31 Jul 2017 14:21:58 +0000 (+0530)
Subject: Don't run ALTER ENUM in an autocommit block on remote nodes
X-Git-Tag: XL_10_R1BETA1~183
X-Git-Url: http://git.postgresql.org/gitweb/static/gitweb.js?a=commitdiff_plain;h=06130a5602ed83ab7b450e46b10173c926b241b5;p=postgres-xl.git

Don't run ALTER ENUM in an autocommit block on remote nodes

Before PG 10, Postgres did not allow ALTER ENUM to be run inside a transaction
block. So we used to run these commands in auto-commit mode on the remote
nodes. But now Postgres has removed the restriction. So we also run the
statements in transaction block.

This fixes regression failures in the 'enum' test case.
---

diff --git a/src/backend/tcop/utility.c b/src/backend/tcop/utility.c
index 1f00a4c651..f700207272 100644
--- a/src/backend/tcop/utility.c
+++ b/src/backend/tcop/utility.c
@@ -2160,7 +2160,7 @@ ProcessUtilitySlow(ParseState *pstate,
 				 */
 				if (IS_PGXC_LOCAL_COORDINATOR)
 					ExecUtilityStmtOnNodes(queryString, NULL, sentToRemote,
-							true, EXEC_ON_ALL_NODES, false);
+							false , EXEC_ON_ALL_NODES, false);
 #endif
 				break;