From 9c3844bbcad96179b2f0ffb34e87e762f116d303 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Tue, 8 Jun 2021 10:57:39 -0400 Subject: [PATCH] Fix contrib/seg regression test in v11. In 20e36c6d2, I neglected to update seg_1.out (which doesn't exist in newer branches). Per buildfarm, via Andrew Dunstan. Discussion: https://postgr.es/m/7611b36f-7d57-5234-ad68-7d25a81e0f13@dunslane.net --- contrib/seg/expected/seg_1.out | 2 ++ 1 file changed, 2 insertions(+) diff --git a/contrib/seg/expected/seg_1.out b/contrib/seg/expected/seg_1.out index 48abb65bb0c..d4832d73ee6 100644 --- a/contrib/seg/expected/seg_1.out +++ b/contrib/seg/expected/seg_1.out @@ -930,6 +930,7 @@ SELECT '1'::seg <@ '-1 .. 1'::seg AS bool; CREATE TABLE test_seg (s seg); \copy test_seg from 'data/test_seg.data' CREATE INDEX test_seg_ix ON test_seg USING gist (s); +SET enable_indexscan = false; EXPLAIN (COSTS OFF) SELECT count(*) FROM test_seg WHERE s @> '11..11.3'; QUERY PLAN @@ -947,6 +948,7 @@ SELECT count(*) FROM test_seg WHERE s @> '11..11.3'; 143 (1 row) +RESET enable_indexscan; SET enable_bitmapscan = false; EXPLAIN (COSTS OFF) SELECT count(*) FROM test_seg WHERE s @> '11..11.3'; -- 2.39.5