Fix an issue where proconfig for functions was not reset with babelfi…

…sh installed (#2641)

If babelfish is installed the set_sql_dialect is installed. That means we were never resetting the proconfig values for triggers/functions.
One major symptom of this is mVU failure when there are some other extensions installed which change search path in proconfig.

Task: BABEL-4982
Signed-off-by: Tanzeel Khan <[email protected]>

test/JDBC/expected/BABEL_4982.out

@@ -0,0 +1,95 @@
+-- psql
+CREATE SCHEMA s1
+GO
+
+CREATE TABLE s1.babel_4982_t (id VARCHAR(100))
+GO
+
+
+
+CREATE FUNCTION babel_4982_ddl_trigger()
+RETURNS event_trigger AS
+$$
+BEGIN
+INSERT INTO babel_4982_t VALUES (current_setting('search_path'));
+END;
+$$
+SECURITY DEFINER
+SET search_path = s1, pg_catalog, pg_temp
+LANGUAGE plpgsql;
+CREATE EVENT TRIGGER babel_4982_ddl_trigger
+	ON ddl_command_end
+	EXECUTE PROCEDURE babel_4982_ddl_trigger();
+SELECT set_config('search_path', 'master_dbo, sys, '||current_setting('search_path'), false);
+GO
+~~START~~
+text
+master_dbo, sys, "$user", public
+~~END~~
+
+
+SHOW search_path
+GO
+~~START~~
+text
+master_dbo, sys, "$user", public
+~~END~~
+
+
+CREATE TABLE babel_4982_t2 (id INT)
+GO
+
+SHOW search_path
+GO
+~~START~~
+text
+master_dbo, sys, "$user", public
+~~END~~
+
+
+BEGIN
+GO
+
+SHOW search_path
+GO
+~~START~~
+text
+master_dbo, sys, "$user", public
+~~END~~
+
+
+DROP TABLE babel_4982_t2
+GO
+
+SHOW search_path
+GO
+~~START~~
+text
+master_dbo, sys, "$user", public
+~~END~~
+
+
+COMMIT
+GO
+
+-- two entries since two DDLs after trigger was created
+SELECT * FROM s1.babel_4982_t
+GO
+~~START~~
+varchar
+s1, pg_catalog, pg_temp
+s1, pg_catalog, pg_temp
+~~END~~
+
+
+DROP EVENT TRIGGER babel_4982_ddl_trigger
+GO
+
+DROP FUNCTION babel_4982_ddl_trigger
+GO
+
+DROP TABLE s1.babel_4982_t
+GO
+
+DROP SCHEMA s1
+GO

test/JDBC/input/BABEL_4982.mix

@@ -0,0 +1,64 @@
+-- psql
+CREATE SCHEMA s1
+GO
+
+CREATE TABLE s1.babel_4982_t (id VARCHAR(100))
+GO
+
+CREATE FUNCTION babel_4982_ddl_trigger()
+RETURNS event_trigger AS
+$$
+BEGIN
+INSERT INTO babel_4982_t VALUES (current_setting('search_path'));
+END;
+$$
+SECURITY DEFINER
+SET search_path = s1, pg_catalog, pg_temp
+LANGUAGE plpgsql;
+
+CREATE EVENT TRIGGER babel_4982_ddl_trigger
+	ON ddl_command_end
+	EXECUTE PROCEDURE babel_4982_ddl_trigger();
+
+SELECT set_config('search_path', 'master_dbo, sys, '||current_setting('search_path'), false);
+GO
+
+SHOW search_path
+GO
+
+CREATE TABLE babel_4982_t2 (id INT)
+GO
+
+SHOW search_path
+GO
+
+BEGIN
+GO
+
+SHOW search_path
+GO
+
+DROP TABLE babel_4982_t2
+GO
+
+SHOW search_path
+GO
+
+COMMIT
+GO
+
+-- two entries since two DDLs after trigger was created
+SELECT * FROM s1.babel_4982_t
+GO
+
+DROP EVENT TRIGGER babel_4982_ddl_trigger
+GO
+
+DROP FUNCTION babel_4982_ddl_trigger
+GO
+
+DROP TABLE s1.babel_4982_t
+GO
+
+DROP SCHEMA s1
+GO