pgsql: Further improve stability of partition_prune regression test.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Further improve stability of partition_prune regression test.
Date: 2019-11-11 15:33:10
Message-ID: E1iUBgk-0006BK-NC@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Further improve stability of partition_prune regression test.

Commits 4ea03f3f4 et al arranged to filter out row counts in parallel
plans, because those are dependent on the number of workers actually
obtained. Somehow I missed that the 'Rows Removed by Filter' counts
can also vary, so fix that too. Per buildfarm.

This seems worth a last-minute patch because unreliable regression
tests are a serious pain in the rear for packagers.

Like the previous patch, back-patch to v11 where this test was
introduced.

Branch
------
REL_11_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/e72b6c39f0fb455b48632afa0c6e3bed9ecf941e

Modified Files
--------------
src/test/regress/expected/partition_prune.out | 5 +++--
src/test/regress/sql/partition_prune.sql | 1 +
2 files changed, 4 insertions(+), 2 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2019-11-11 19:40:15 pgsql: Doc: fix ancient mistake, or at least obsolete info, in rules ex
Previous Message Peter Eisentraut 2019-11-11 10:55:03 pgsql: gitattributes: Remove entries for no longer existing files