pgsql: Modify create_index regression test to avoid intermittent failur

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Modify create_index regression test to avoid intermittent failur
Date: 2012-04-26 02:58:04
Message-ID: E1SNEuC-0002Ba-Lk@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Modify create_index regression test to avoid intermittent failures.

We have been seeing intermittent buildfarm failures due to a query
sometimes not using an index-only scan plan, because a background
auto-ANALYZE prevented the table's all-visible bits from being set
immediately, thereby causing the estimated cost of an index-only scan
to go up considerably. Adjust the test case so that a bitmap index scan is
preferred instead, which serves equally well for the purpose the test case
is actually meant for. (Of course, it would be better to eliminate the
interference from auto-ANALYZE, but I see no low-risk way to do that,
so any such fix will have to be left for 9.3 or later.)

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/d6d5f67b5b98b1685f9158e9d00a726afb2ae789

Modified Files
--------------
src/test/regress/expected/create_index.out | 22 ++++++++++++----------
src/test/regress/sql/create_index.sql | 6 +++---
2 files changed, 15 insertions(+), 13 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2012-04-26 17:09:38 pgsql: psql: Tab completion updates
Previous Message Tom Lane 2012-04-26 00:21:05 pgsql: Fix planner's handling of RETURNING lists in writable CTEs.