From cba0fe024e35839688e3a3d256d1dcdf50baadaf Mon Sep 17 00:00:00 2001 From: Thomas Munro Date: Tue, 9 Jul 2019 18:11:01 +1200 Subject: [PATCH] Force hash joins to be enabled in the hash join regression tests. Otherwise the regressplans.sh tests generate extremely slow nested loop joins. Back-patch to 11 where the hash join tests came in. Reported-by: Michael Paquier Discussion: https://postgr.es/m/20190708055256.GB2709%40paquier.xyz --- src/test/regress/expected/join_hash.out | 1 + src/test/regress/sql/join_hash.sql | 1 + 2 files changed, 2 insertions(+) diff --git a/src/test/regress/expected/join_hash.out b/src/test/regress/expected/join_hash.out index 9eee39bdd3..6080ebb961 100644 --- a/src/test/regress/expected/join_hash.out +++ b/src/test/regress/expected/join_hash.out @@ -4,6 +4,7 @@ begin; set local min_parallel_table_scan_size = 0; set local parallel_setup_cost = 0; +set local enable_hashjoin = on; -- Extract bucket and batch counts from an explain analyze plan. In -- general we can't make assertions about how many batches (or -- buckets) will be required because it can vary, but we can in some diff --git a/src/test/regress/sql/join_hash.sql b/src/test/regress/sql/join_hash.sql index ae352e9b0b..5b41d01a24 100644 --- a/src/test/regress/sql/join_hash.sql +++ b/src/test/regress/sql/join_hash.sql @@ -6,6 +6,7 @@ begin; set local min_parallel_table_scan_size = 0; set local parallel_setup_cost = 0; +set local enable_hashjoin = on; -- Extract bucket and batch counts from an explain analyze plan. In -- general we can't make assertions about how many batches (or -- 2.40.0