From 3955c50f3762be6f0a63573c5b4efef72b30dc2b Mon Sep 17 00:00:00 2001 From: Thomas Munro Date: Tue, 9 Jul 2019 18:24:33 +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.out | 1 + src/test/regress/sql/join.sql | 1 + 2 files changed, 2 insertions(+) diff --git a/src/test/regress/expected/join.out b/src/test/regress/expected/join.out index d63cf442a1b..db4b9c29e5c 100644 --- a/src/test/regress/expected/join.out +++ b/src/test/regress/expected/join.out @@ -5998,6 +5998,7 @@ drop table j3; 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.sql b/src/test/regress/sql/join.sql index 19eb782cb0f..259c7c7a65e 100644 --- a/src/test/regress/sql/join.sql +++ b/src/test/regress/sql/join.sql @@ -2032,6 +2032,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