From: Tomas Vondra <tomas.vondra@postgresql.org>
Date: Mon, 6 Apr 2020 21:58:10 +0000 (+0200)
Subject: Fix failures in incremental_sort due to number of workers
X-Git-Tag: aio-before-rebase-2020-06-24~565
X-Git-Url: http://git.postgresql.org/gitweb/review?a=commitdiff_plain;h=23ba3b5ee278847e4fad913b80950edb2838fd35;p=users%2Fandresfreund%2Fpostgres.git

Fix failures in incremental_sort due to number of workers

The last test in incremental_sort suite prints a parallel plan, but some
of the buildfarm animals have custom max_parallel_workers_per_gather
values, causing failures. Fixed by setting the GUC to an explicit value.

Discussion: https://postgr.es/m/CAPpHfds1waRZ=NOmueYq0sx1ZSCnt+5QJvizT8ndT2=etZEeAQ@mail.gmail.com
---

diff --git a/src/test/regress/expected/incremental_sort.out b/src/test/regress/expected/incremental_sort.out
index f130c606c8..404de63094 100644
--- a/src/test/regress/expected/incremental_sort.out
+++ b/src/test/regress/expected/incremental_sort.out
@@ -1402,6 +1402,7 @@ set min_parallel_table_scan_size = '1kB';
 set min_parallel_index_scan_size = '1kB';
 set parallel_setup_cost = 0;
 set parallel_tuple_cost = 0;
+set max_parallel_workers_per_gather = 2;
 create table t (a int, b int, c int);
 insert into t select mod(i,10),mod(i,10),i from generate_series(1,10000) s(i);
 create index on t (a);
diff --git a/src/test/regress/sql/incremental_sort.sql b/src/test/regress/sql/incremental_sort.sql
index 3b359efa29..2ba5d7a67d 100644
--- a/src/test/regress/sql/incremental_sort.sql
+++ b/src/test/regress/sql/incremental_sort.sql
@@ -198,6 +198,7 @@ set min_parallel_table_scan_size = '1kB';
 set min_parallel_index_scan_size = '1kB';
 set parallel_setup_cost = 0;
 set parallel_tuple_cost = 0;
+set max_parallel_workers_per_gather = 2;
 
 create table t (a int, b int, c int);
 insert into t select mod(i,10),mod(i,10),i from generate_series(1,10000) s(i);