mirror of
https://github.com/postgres/postgres.git
synced 2025-06-11 20:28:21 +03:00
Stabilize contrib/seg regression test.
If autovacuum comes along just after we fill table test_seg with
some data, it will update the stats to the point where we prefer
a plain indexscan over a bitmap scan, breaking the expected
output (as well as the point of the test case). To fix, just
force a bitmap scan to be chosen here.
This has evidently been wrong since commit de1d042f5
. It's not
clear why we just recently saw any buildfarm failures due to it;
but prairiedog has failed twice on this test in the past week.
Hence, backpatch to v11 where this test case came in.
This commit is contained in:
@ -217,9 +217,11 @@ CREATE TABLE test_seg (s seg);
|
||||
|
||||
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';
|
||||
SELECT count(*) FROM test_seg WHERE s @> '11..11.3';
|
||||
RESET enable_indexscan;
|
||||
|
||||
SET enable_bitmapscan = false;
|
||||
EXPLAIN (COSTS OFF)
|
||||
|
Reference in New Issue
Block a user