From f9245510bca25c61de83a44726fea7daadde5f80 Mon Sep 17 00:00:00 2001 From: SaitTalhaNisanci Date: Mon, 30 Nov 2020 19:32:49 +0300 Subject: [PATCH] Run pg12 and pg13 separately (#4352) It seems that sometimes we get `too many clients errors` with this set of parallel tests, hence two of them are separated. (cherry picked from commit 8c3dd6338e79423e84e3b71fff0d4c680e21a2d7) --- src/test/regress/multi_schedule | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/src/test/regress/multi_schedule b/src/test/regress/multi_schedule index f29006bd1..aa393a600 100644 --- a/src/test/regress/multi_schedule +++ b/src/test/regress/multi_schedule @@ -85,7 +85,8 @@ test: set_operation_and_local_tables test: subqueries_deep subquery_view subquery_partitioning subquery_complex_target_list subqueries_not_supported subquery_in_where test: non_colocated_leaf_subquery_joins non_colocated_subquery_joins non_colocated_join_order -test: subquery_prepared_statements pg12 cte_inline pg13 recursive_view_local_table +test: subquery_prepared_statements cte_inline recursive_view_local_table +test: pg13 pg12 test: tableam drop_column_partitioned_table # ---------- @@ -101,7 +102,8 @@ test: multi_explain hyperscale_tutorial partitioned_intermediate_results distrib test: multi_basic_queries cross_join multi_complex_expressions multi_subquery multi_subquery_complex_queries multi_subquery_behavioral_analytics test: multi_subquery_complex_reference_clause multi_subquery_window_functions multi_view multi_sql_function multi_prepare_sql test: sql_procedure multi_function_in_join row_types materialized_view undistribute_table -test: multi_subquery_in_where_reference_clause adaptive_executor propagate_set_commands geqo +test: multi_subquery_in_where_reference_clause adaptive_executor propagate_set_commands +test: geqo # this should be run alone as it gets too many clients test: join_pushdown test: multi_subquery_union multi_subquery_in_where_clause multi_subquery_misc statement_cancel_error_message