Fix plan instability in the new tuplesort test.

anarazel · anarazel · commit 80ef34fc7075 · 2019-11-13T16:36:31.000-08:00
At least buildfarm member florican doesn't use a material node above a
sort in the mark/restore case. As material is not intended to be
tested with that query, disallow.
diff --git a/src/test/regress/expected/tuplesort.out b/src/test/regress/expected/tuplesort.out
@@ -603,6 +603,7 @@ INSERT INTO test_mark_restore(col1, col2, col12)
 BEGIN;
 SET LOCAL enable_nestloop = off;
 SET LOCAL enable_hashjoin = off;
+SET LOCAL enable_material = off;
 -- set query into variable once, to avoid repetition of the fairly long query
 SELECT $$
     SELECT col12, count(distinct a.col1), count(distinct a.col2), count(distinct b.col1), count(distinct b.col2), count(*)
@@ -664,11 +665,10 @@ EXPLAIN (COSTS OFF) :qry;
                      ->  Sort
                            Sort Key: a.col12 DESC
                            ->  Seq Scan on test_mark_restore a
-                     ->  Materialize
-                           ->  Sort
-                                 Sort Key: b.col12 DESC
-                                 ->  Seq Scan on test_mark_restore b
-(15 rows)
+                     ->  Sort
+                           Sort Key: b.col12 DESC
+                           ->  Seq Scan on test_mark_restore b
+(14 rows)
 
 :qry;
  col12 | count | count | count | count | count 
diff --git a/src/test/regress/sql/tuplesort.sql b/src/test/regress/sql/tuplesort.sql
@@ -275,6 +275,7 @@ BEGIN;
 
 SET LOCAL enable_nestloop = off;
 SET LOCAL enable_hashjoin = off;
+SET LOCAL enable_material = off;
 
 -- set query into variable once, to avoid repetition of the fairly long query
 SELECT $$
