From 8b0aed521f6ba4bf4f42cff73db87b0a9c96cb46 Mon Sep 17 00:00:00 2001 From: Sait Talha Nisanci Date: Tue, 1 Dec 2020 00:00:17 +0300 Subject: [PATCH] Isolate join test Join test gets too many clients error too frequently hence we should not run anything concurrently with that. Hopefully this will fix the flakiness of test. --- src/test/regress/multi_schedule | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/src/test/regress/multi_schedule b/src/test/regress/multi_schedule index 24c6d2548..d026b2e89 100644 --- a/src/test/regress/multi_schedule +++ b/src/test/regress/multi_schedule @@ -97,8 +97,9 @@ 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 -test: join geqo +test: multi_subquery_in_where_reference_clause adaptive_executor propagate_set_commands geqo +# this should be run alone as it gets too many clients +test: join test: multi_subquery_union multi_subquery_in_where_clause multi_subquery_misc statement_cancel_error_message test: multi_agg_distinct multi_agg_approximate_distinct multi_limit_clause_approximate multi_outer_join_reference multi_single_relation_subquery multi_prepare_plsql set_role_in_transaction test: multi_reference_table multi_select_for_update relation_access_tracking pg13_with_ties